Re: oslevel - unable to acquire lock
From: Timothy J. Bogart (tjb_at_starbase.starbaseunix.org)
Date: 10/09/03
- Next message: Dan Foster: "Re: PP size: 32MB vs. 64MB"
- Previous message: Chris: "PP size: 32MB vs. 64MB"
- In reply to: Nicholas Dronen: "Re: oslevel - unable to acquire lock"
- Next in thread: Dan Foster: "Re: oslevel - unable to acquire lock"
- Reply: Dan Foster: "Re: oslevel - unable to acquire lock"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 9 Oct 2003 09:46:05 -0500
In article <3f84962a$0$194$75868355@news.frii.net>,
Nicholas Dronen <ndronen@io.frii.com> wrote:
>Victor Lee <vilee@amdocs.com> wrote:
>VL> Hi
>
>VL> when I run the command 'oslevel' it gives an error saying 'unable to
>VL> acquire lock'. Does anyone know how to fix this?
>
>Sounds like a process locked one of the ODM files and died before
>unlocking it. I don't know the how-to for this. I'd start by
>looking for files in /etc/objrepos and /usr/lib/objrepos with
>names like "lock."
>
When I last ran into this, IBM said /usr was full. At the time, they were right. 8-)
-- "I'm a big fan of ignorance based techniques, because humans have a lot of ignorance, and we want to play our strong suit." Eric Lander New Scientist
- Next message: Dan Foster: "Re: PP size: 32MB vs. 64MB"
- Previous message: Chris: "PP size: 32MB vs. 64MB"
- In reply to: Nicholas Dronen: "Re: oslevel - unable to acquire lock"
- Next in thread: Dan Foster: "Re: oslevel - unable to acquire lock"
- Reply: Dan Foster: "Re: oslevel - unable to acquire lock"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|