From: Kenny Hitt <kenny@hittsjunk.net>
To: Rejean Proulx <rejean@interfree.ca>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: Problem With apt-get update
Date: Mon, 11 Apr 2005 09:58:04 -0500 [thread overview]
Message-ID: <20050411145804.GB29837@blackbox> (raw)
In-Reply-To: <293742474.20050411070600@interfree.ca>
Hi.
I get a message like that if I try to do something as a normal
user that should only be done as root.
The other time it can happen is if I am already using apt as
root in another console.
That file is what it's name says: a lock file to keep two things
from writing to the same database.
Hope this helps.
Kenny
On Mon, Apr 11, 2005 at 07:06:00AM -0400, Rejean Proulx wrote:
> I am getting the following message from my Debian Linux. What should
> the owner and permissions be for
>
> /var/lib/apt/lists/lock
>
> E: Could not get lock /var/lib/apt/lists/lock - open (11 Resource temporarily unavailable)
> E: Unable to lock the list directory
>
> __________ NOD32 1.1055 (20050411) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com
>
>
> ===8<===========End of original message text===========
>
>
> --
> Best regards,
> Rejean mailto:rejean@interfree.ca
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DKvF3-0000Hj-00@interfree.ca>
` Rejean Proulx
` Kenny Hitt [this message]
` jim grimsby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050411145804.GB29837@blackbox \
--to=kenny@hittsjunk.net \
--cc=rejean@interfree.ca \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).