Bug#11094: Policy should mention that serial lines require UUCP-style locking
Hi,
The FHS, now included by policy, already lays this out in
detail. I think there is no need to duplicate this in policy itself
(given the size the document has evolved to, any such redundancy is
undesirable).
I am closing this report; if you feel that this can pass
muster in a new policy process, please feel free to reopen and push a
proposal through.
manoj
======================================================================
5.6 /var/lock : Lock files
Lock files should be stored within the /var/lock directory structure.
Device lock files, such as the serial device lock files that were
originally found in either /usr/spool/locks or /usr/spool/uucp, must now
be stored in /var/lock. The naming convention which must be used is
"LCK.." followed by the base name of the device. For example, to lock
/dev/cua0 the file "LCK..cua0" would be created.
The format used for device lock files must be the HDB UUCP lock file
format. The HDB format is to store the process identifier (PID) as a
ten byte ASCII decimal number, with a trailing newline. For example, if
process 1230 holds a lock file, it would contain the eleven characters:
space, space, space, space, space, space, one, two, three, zero, and
newline.
Then, anything wishing to use /dev/cua0 can read the lock file and act
accordingly (all locks in /var/lock should be world-readable).
======================================================================
--
In article <1133@gort.cs.utexas.edu> Jason bitches about IBM screwing
all of the people who were dumb enough to buy RTs, then... Rad
Morrison
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: