This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 09/03/2011 19:29, Thomas Wolff wrote:This is wrong on several counts.For example if cygwin is still installed on a FAT drive (I know ...) it may be useful (for all users) to switch /tmp to an NTFS directory (e.g. XWin used to fail with a FAT /tmp for a while).
XWin still fails with /tmp on FAT. This is because XWin uses hardlinks to create it's lock file, and cygwin can't support hardlinks on FAT because the filesystem doesn't support them.
XWin uses the literal path /tmp. A lock file which appears in a different place depending on an environment variable wouldn't be much of a lock file.
Oops, you're right. Actually the workaround I used here is to remount /tmp ('mount -f C:/tmp /tmp' in a profile; I could have checked that...)
If you actually have this problem with XWin, you should use the server option -nolock.
-- 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
-- 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
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |