Message-ID: <543B7765.6050004@ladisch.de>
Date: Mon, 13 Oct 2014 08:55:33 +0200
From: Clemens Ladisch <clemens@ladisch.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Gene Heskett <gheskett@wdtv.com>, linux-kernel@vger.kernel.org
Subject: Re: reboot housekeeping, lack thereof, is messing with me
References: <201410121321.26582.gheskett@wdtv.com>
In-Reply-To: <201410121321.26582.gheskett@wdtv.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

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.


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/