diff options
author | Christopher Faylor <me@cgf.cx> | 2011-12-17 23:39:47 +0000 |
---|---|---|
committer | Christopher Faylor <me@cgf.cx> | 2011-12-17 23:39:47 +0000 |
commit | 1b23b30b29eebbe7c9953f2a7470f31a0feb8702 (patch) | |
tree | 10592e165f5e31aac70913190d50d700f6fec96c /winsup/cygwin/flock.cc | |
parent | 988d896c0a3b60fab9cd323e52eefd4af98be323 (diff) | |
download | cygnal-1b23b30b29eebbe7c9953f2a7470f31a0feb8702.tar.gz cygnal-1b23b30b29eebbe7c9953f2a7470f31a0feb8702.tar.bz2 cygnal-1b23b30b29eebbe7c9953f2a7470f31a0feb8702.zip |
Clean up whitespace.
Diffstat (limited to 'winsup/cygwin/flock.cc')
-rw-r--r-- | winsup/cygwin/flock.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/winsup/cygwin/flock.cc b/winsup/cygwin/flock.cc index d88cb418b..bd508719c 100644 --- a/winsup/cygwin/flock.cc +++ b/winsup/cygwin/flock.cc @@ -1028,7 +1028,7 @@ lf_setlock (lockf_t *lock, inode_t *node, lockf_t **clean, HANDLE fhdl) } /* Wait for the blocking object and, for POSIX locks, its holding process. - Unfortunately, since BSD flock locks are not attached to a specific + Unfortunately, since BSD flock locks are not attached to a specific process, we can't recognize an abandoned lock by sync'ing with the creator process. We have to make sure the event object is in a signalled state, or that it has gone away. The latter we can only |