3.0.7(0.338/5/3): Possible reference to Developer's instances of dev files in deployed build

[Norton Allen]

On 12/5/2019 2:44 PM, Ken Brown wrote:
> Then I wonder what's different about Wilfed's setup that causes an attempt to
> open Z: when it's offline.
>
> I'm grasping at straws, but could the difference be related to the fact that his
> drive Z: is not a Samba share?  Here's an excerpt from the mount output in one
> of his earlier emails (when Z: is online):
>
> V: on /cygdrive/v type smbfs (binary,noacl,posix=0,user,noumount,auto)
> W: on /cygdrive/w type smbfs (binary,noacl,posix=0,user,noumount,auto)
> X: on /cygdrive/x type smbfs (binary,noacl,posix=0,user,noumount,auto)
> Y: on /cygdrive/y type smbfs (binary,noacl,posix=0,user,noumount,auto)
> Z: on /cygdrive/z type cifs (binary,noacl,posix=0,user,noumount,auto)
>                          ^^^^

Correct me if I'm wrong or misremembering, but I think Corinna 
specifically set 'always available offline', and I do not believe the OP 
used that configuration. I have network drives which are only accessible 
when I am at work, and I do not have 'always available offline' 
selected, yet they are able to persist across sessions where they are 
inaccessible.

I'm sorry to say though that I have not followed this discussion closely 
enough to attempt to reproduce the problem myself.



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple