Jan Minar wrote:
Seems like your messing with switching from root to tom, back and forth.
Maybe another users too. Also seems you omit to note what actualy
happens (null strace). Fetchmail works as it should, check the
/home/tom permissions. Check the ownership and permissions of
/home/tom, and
On Mon, Jan 05, 2004 at 08:02:19PM -0500, Thomas H. George wrote:
> Final two lines of strace fetchmail run from /home/tom:
>
>open("/home/tom/.fetchmail.pid", O_WRONLY|O_CREAT|O_EXCL|O_SYNC,
> 0666) = -1 EACCESS (Permission Denied)
This clearly means the program didn't have the write permis
chmail run from /home/tom:
open("/home/tom/.fetchmail.pid", O_WRONLY|O_CREAT|O_EXCL|O_SYNC,
0666) = -1 EACCESS (Permission Denied)
write (2, "fetchmail: lock creation failed. ..., 33) = 33
I tried creating a file .fetchmail.pid with chown tom and chmod 666.
This gave the s
On Mon, Jan 05, 2004 at 09:41:55AM -0500, Thomas H. George wrote:
> With no fetchmail to feed mail to mutt and so no threading I have lost
> the thread and must re-post.
If you want to read the thread, look among the headers of any mail on
this list, for `List-Archive:'.
> As advised I re-copied
With no fetchmail to feed mail to mutt and so no threading I have lost
the thread and must re-post.
As advised I re-copied /oldhome/tom to /home/tom with tar. This did not
solve the problem.
There is no .fetchmail.pid file in /oldhome/tom or anywhere else.
I tried dpkg -- purge fetchmail foll
Hi, Thomas.
On Sat, Jan 03, 2004 at 10:49:55AM -0500, Thomas H. George wrote:
> I am in the process of replacing a failing hard drive. I copied my home
> directory from the old drive to the new drive with
>
>cd /oldhome/tom
>cp -Rp .* /home/tom ( Found by trial and error t
On Saturday 03 January 2004 16:45, GCS wrote:
> On Sat, Jan 03, 2004 at 04:45:26PM +, Richard Lyons wrote:
> > > show tom.tom on every file.
> >
> > If he has a tom.tom on every file, he can use them to send the
> > messages, together with a few smoke signals, and save bothering to
> > set up e
On Sat, Jan 03, 2004 at 04:45:26PM +, Richard Lyons <[EMAIL PROTECTED]> wrote:
> > Depends. Are you sure that /home/tom/ and everything under that is
> > owned by you? 'ls -ld /home/tom' and 'ls -la /home/tom' should show
> > tom.tom on every file.
>
> If he has a tom.tom on every file, he ca
On Saturday 03 January 2004 16:00, GCS wrote:
> On Sat, Jan 03, 2004 at 10:49:55AM -0500, Thomas H. George
<[EMAIL PROTECTED]> wrote:
> >cd /oldhome/tom
> >cp -Rp .* /home/tom ( Found by trial and error
> > that .* works)
> >
> > Almost everything works - e.g. mozilla previou
On Sat, Jan 03, 2004 at 10:49:55AM -0500, Thomas H. George <[EMAIL PROTECTED]> wrote:
>cd /oldhome/tom
>cp -Rp .* /home/tom ( Found by trial and error that .*
> works)
>
> Almost everything works - e.g. mozilla previously undeleted mail - but
> fetchmail which aborts with t
I am in the process of replacing a failing hard drive. I copied my home
directory from the old drive to the new drive with
cd /oldhome/tom
cp -Rp .* /home/tom ( Found by trial and error that .*
works)
Almost everything works - e.g. mozilla previously undeleted mail - but
f
>spock> fetchmail: lock creation failed.
>spock> So I'm assuming that some flag has been set so that
>spock> fetchmail thinks it is still open or something
>
> In non-root mode fetchmail is supposed to use a lockfile named
> ~/.fetchmail.pid which
"spock" == spock <[EMAIL PROTECTED]> writes:
spock> generated an error (forgotten now). Sorry to be vague, but
spock> this happened a few weeks ago. Since then, every time I try
spock> and fetchmail, I get the message:
spock> fetchmail: lock cre
ued. Only by holding down CTRL-C
(I think it was) did I manage to stop it, which generated an
error (forgotten now). Sorry to be vague, but this happened a
few weeks ago. Since then, every time I try and fetchmail,
I get the message:
fetchmail: lock creation failed.
So I'm assuming that some
14 matches
Mail list logo
