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
Hi,
Generally, the basic idea is that each program that uses a serial port
writes a file in /var/lock with the name, as I recall, LCK..portname.
Inside that file, I believe, is stored the PID of that process. The
file is removed when the port is no loinger used. Various serial port
programs use
John,
You originally proposed the following amendment to policy:
There is no mention of the UUCP-style locking required for serial
lines to prevent multiple communications programs from attempting to
use the same line at once. For a brief description of UUCP-style
serial locking, see the
3 matches
Mail list logo
