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-next>] [day] [month] [year] [list]
Date:	Sun, 12 Oct 2014 13:21:26 -0400
From:	Gene Heskett <>
Subject: reboot housekeeping, lack thereof, is messing with me

To whomever is in charge of the supposedly volatile LCK.. files in 

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?

/var/lock is not now nor has it ever been volatile storage since its on 
the drive forever, or until one becomes root, deletes it, and then reboots 
the machine.  That just cost me a days work, testing usb cables etc with a 
digital storage scope and a chip replacement on the other systems 
motherboard that in all likelyhood wasn't needed.

Is this fixable?


Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
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