Complete.Org: Mailing Lists: Archives: discussion: May 2000:
[aclug-L] Re: unlocking lock files

[aclug-L] Re: unlocking lock files

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: discussion@xxxxxxxxx
Subject: [aclug-L] Re: unlocking lock files
From: Nate Bargmann <n0nb@xxxxxxxxxxxxxxxx>
Date: Thu, 18 May 2000 05:23:24 -0500
Reply-to: discussion@xxxxxxxxx

On Thu, May 18, 2000 at 03:43:16AM -0500, Michael Holmes wrote:
> First thing I tried.   Also KDe/console/lock
> No luck, I was so happy to have sound, for one night!

Hmmm.  Have you checked the permissions on that file?  Could it be
that it's marked read only or some such?  I'm curious what KDE/console/
lock does...that sounds like a password protection of your computer,
not a program "locking" a device with a lock file to prevent other
programs from using said device or a program designed to remove stale
locks, but I could be wrong as I've used KDE very little.

Generally a lock file lives in /var/lock and is the name of the device
being locked and its contents are the PID of the process that "owns"
the device.  If you locate database is setup you can use locate audio
and see if you can find the file or use the find command (the exact
syntax escapes me).

- Nate >>


 Wireless | Amateur Radio Station N0NB          | "None can love freedom
 Internet | n0nb@xxxxxxxxxxxxxxxx               | heartily, but good
 Location | Wichita, Kansas USA EM17hs          | men; the rest love not
   Wichita area exams; ham radio; Linux info @  | freedom, but license."
              | -- John Milton

-- This is the discussion@xxxxxxxxx list.  To unsubscribe,

[Prev in Thread] Current Thread [Next in Thread]