#15 LCK.. file is not FHS compliant

[Marc Haber]

Hi,

ser2net writes its process name to the LCK file locking the serial port, while the FHS specifies that lock files need to be in 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.

To me, the process name does not look to be compliant.

Or, are there multiple standards competing with each other?

Greetings
Marc

[Corey Minyard]

Should be fixed in 2.8-rc4 or 2.9