Package: minicom
Version: 2.3-1
When starting 'minicom' contents of lock file is not to Filesystem Hierarchy
Standard. FHS 2.3 states:
"/var/lock : Lock files
Purpose
Lock files should be stored within the /var/lock directory structure.
Lock files for devices and other resources shared by multiple applications,
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/ttyS0 the file "LCK..ttyS0" would be
created. [40]
The format used for the contents of such 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."
Minicom has been started in another terminal, connecting to '/dev/ttyS0'.
Minicom stores the following in the lock file:
dcla...@humboldt:~$ cd /var/lock
dcla...@humboldt:/var/lock$ ls
LCK..ttyS0
dcla...@humboldt:/var/lock$ cat LCK..ttyS0
5097 minicom dclarke
I suggest minicom package use package 'lockdev' for locking.
I am using Debian GNU/Linux 5.04, kernel 2.6.26-2-686 #1 SMP.
--
Dave Clarke
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
