lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 13 Oct 2014 08:55:33 +0200
From:	Clemens Ladisch <>
To:	Gene Heskett <>,
Subject: Re: reboot housekeeping, lack thereof, is messing with me

Gene Heskett wrote:
> To whomever is in charge of the supposedly volatile LCK.. files in
> /var/lock:

Whoever that may be, it's not the kernel.

> Its my understanding that these files should be volatile when they
> represent a USB usage, because a USB device can be unplugged instantly and
> at any time.  The device nicely and dutifully disappears from an 'ls /dev'
> listing when a device is unplugged.
> Why is it then that the /var/lock/LCK..ttyUSB1 file is always left behind,
> so it screws up any possibility of doing a nice clean reboot and restart
> of the program that uses it?

What program leaves this file behind?  (The pid in there is no longer
helpful, unless it got logged due to a segfault, but what was the last
program used for serial stuff?)

Anyway, it appears some programs automatically delete this file when the
pid is not valid.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists