On May 11 09:34, Corinna Vinschen wrote: > On May 10 15:07, Andrew Schulman wrote: > > > a session that I detached on the same tty just seconds before. > > > > > > 3. chmod 666 on the socket file did not work (its permissions were > > > already 644, owned my 'morse', as shown in my original session long). > > > > No, I suggested that you try 0600, on the theory that your 0640 permissions > > might be too permissive, and screen would refuse to use the socket. > > Unlikely, but worth a try. > > > > However, if your socket is on a FAT file system, I don't know if you can > > set 0600 permissions. > > > > > HOWEVER, I am wondering: my Cygin /tmp *IS* on a FAT32 filesystem, *NOT* > > > an NTFS filesystem. Would that matter? Are socket files properly > > > handled by Cygwin on FAT32? (I've never used a socket-based Cygwin > > > program on this host before, at least not to my knowledge.) > > > > Hm, that could explain it. I don't recall this coming up before. > > AF_LOCAL/AF_UNIX sockets are handled on all file systems.
Correction: AF_LOCAL/AF_UNIX sockets are handled on all file systems which support DOS attributes. They don't work on NFS, for instance. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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