From: Ted Stern <stern+gnus@cray.com>
Subject: Re: movemail dies on me.
Date: Fri, 17 Oct 2003 13:22:10 -0700 [thread overview]
Message-ID: <ycc4qy7zkb1.fsf@monkeypuzzle.wc.cray.com> (raw)
In-Reply-To: <m3znfzbrso.fsf@quimbies.gnus.org>
On 17 Oct 2003, Lars Magne Ingebrigtsen wrote:
> Gaute B Strokkenes <biggaute@uwc.net> writes:
>
>> For some time now, I have occasionally had to deal with queries like
>> this:
>>
>> movemail: (Drept return). Continue? (yes or no)
>
> [...]
>
>> Unfortunately I'm finding this rather hard to debug. movemail is
>> suid so that it can manipulate my mail spool, and the intermittent
>> nature doesn't help either. Is anyone else seeing this?
>
> Haven't heard of anything like that before.
I just started an emacs compiled for Linux that is otherwise identically set
as on my emacs compiled for Solaris 2.8. I have mail-sources looking in an
incoming spool directory, and suddenly I get a message like this:
movemail: No locks available for /users/stern/mail/incoming/lists.linux.spool (1 return). Continue? (yes or no)
(not sure if that cut and paste worked ... the region is read only (?!) so I'm
copying it below.
movemail: No locks available for <myhomedir>/mail/incoming/somefolder.spool \
(1 return). Continue? (yes or no)
For me, this happens every time I try to read new mail.
--
Ted Stern Applications Group
Cray Inc. office: 206-701-2182
411 First Avenue South, Suite 600 cell: 206-383-1049
Seattle, WA 98104-2860 FAX: 206-701-2500
Frango ut patefaciam -- I break that I may reveal
(The Paleontological Society motto, equally apropos for debugging)
next prev parent reply other threads:[~2003-10-17 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 8:00 Gaute B Strokkenes
2003-10-17 19:14 ` Lars Magne Ingebrigtsen
2003-10-17 20:13 ` Gaute B Strokkenes
2003-10-17 20:22 ` Ted Stern [this message]
2003-10-17 21:11 ` Lars Magne Ingebrigtsen
2003-10-17 22:58 ` Ted Stern
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=ycc4qy7zkb1.fsf@monkeypuzzle.wc.cray.com \
--to=stern+gnus@cray.com \
/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 NNTP newsgroup(s).