[plug] pine problems. + dump

Shayne O'Neill shayne at guild.murdoch.edu.au
Wed May 11 13:50:46 WST 2005


To clarify by 'just has this huge loop of', I mean 'has this huge loop of
xxxx at the end of it'

--
 I wish a robot would get elected president. That way, when he came to
town, we could all take a shot at him and not feel too bad.
- Jack Handey (And now, Deep thoughts)

On Wed, 11 May 2005, Shayne O'Neill wrote:

>
> Ok. I just ran strace -odump pine
>
> and the dump file just has this huge loop of;-
>
> sigreturn()                             = ? (mask now [])
> flock(4, LOCK_SH)                       = ? ERESTARTSYS (To be restarted)
> --- SIGALRM (Alarm clock) @ 0 (0) ---
> rt_sigprocmask(SIG_BLOCK, [ALRM], [ALRM], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [ALRM], [ALRM], 8) = 0
> rt_sigprocmask(SIG_BLOCK, [ALRM], [ALRM], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [ALRM], [ALRM], 8) = 0
> gettimeofday({1115789397, 255782}, {4294966816, 0}) = 0
> rt_sigprocmask(SIG_BLOCK, [ALRM], [ALRM], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [ALRM], [ALRM], 8) = 0
> time(NULL)                              = 1115789397
> write(1, "\33[3m\33[42;70H|\33[23m\33[42;1H", 25) = 25
> rt_sigaction(SIGALRM, {0x8157fc8, [], SA_RESTART}, {0x8157fc8, [],
> SA_RESTART}, 8) = 0
> alarm(1)                                = 0
> sigreturn()                             = ? (mask now [])
> flock(4, LOCK_SH)                       = ? ERESTARTSYS (To be restarted)
> --- SIGALRM (Alarm clock) @ 0 (0) ---
>
> Theres a reference to shayne.lock , before
>
> gettimeofday({1115789392, 268632}, {4294966816, 0}) = 0
> rt_sigprocmask(SIG_BLOCK, [ALRM], [], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], [ALRM], 8) = 0
> lstat64("/var/spool/mail/shayne.lock", {st_mode=S_IFREG|0666, st_size=0,
> ...}) = 0
> time(NULL)                              = 1115789392
> umask(0)                                = 022
> getpid()                                = 21307
> time(NULL)                              = 1115789392
> uname({sys="Linux", node="perthimc.asn.au", ...}) = 0
> open("/var/spool/mail/shayne.lock.1115789392.21307.perthimc.asn.au",
> O_WRONLY|O_CREAT|O_EXCL, 0666) = 4
> close(4)                                = 0
> link("/var/spool/mail/shayne.lock.1115789392.21307.perthimc.asn.au",
> "/var/spool/mail/shayne.lock") = -1 EEXIST (File exists)
> stat64("/var/spool/mail/shayne.lock.1115789392.21307.perthimc.asn.au",
> {st_mode=S_IFREG|0666, st_size=0, ...}) = 0
> unlink("/var/spool/mail/shayne.lock.1115789392.21307.perthimc.asn.au") = 0
> umask(022)                              = 0
> time(NULL)                              = 1115789392
>
> After this then it starts losing its temper and starts repeating that
> first block I displayed endlessly in loops.
>
> Any ideas what this might be?
>
> --
>  I wish a robot would get elected president. That way, when he came to
> town, we could all take a shot at him and not feel too bad.
> - Jack Handey (And now, Deep thoughts)
>
> On Wed, 11 May 2005, Shayne O'Neill wrote:
>
> >
> > seems to be a mbox. By the look of it, blowing away the pine-debug and
> > pinerc files isnt working. (As was suggested to me offlist).
> >
> > Hmm. Maybe it is unicode crap. Bloody spammers.
> >
> > --
> >  I wish a robot would get elected president. That way, when he came to
> > town, we could all take a shot at him and not feel too bad.
> > - Jack Handey (And now, Deep thoughts)
> >
> > On Wed, 11 May 2005, W.Kenworthy wrote:
> >
> > > mbox or .maildir or imap access?
> > >
> > > Check out files with unknown/control chars in them: sometimes happens
> > > with unicode subject lines (Chinese glyphs etc).  Can upset the mail
> > > reader when trying to read the file (worse with mbox as it breaks the
> > > whole file, not just one message!)
> > >
> > > seen this on corrupted mbox files (does anyone use them these days?)
> > >
> > > also seen it on a corrupted filesystem: if using ext2/3 and .maildir, do
> > > yourself a favour and upgrade to reiserfs or one of the other
> > > journalling filesystems (no flames please: I got sick of losing data to
> > > ext2/3 and have not had a problem on that machine since changing to
> > > reiserfs)
> > >
> > > pine's imap support was always a bit clunky, but imap provided a good
> > > buffer between problems like this
> > >
> > > I have pine setup as a fallback/text mailreader but since getting
> > > webmail up at home I have not bothered with (~18mnths or so) and imap
> > > was the answer back then.
> > >
> > > BillK
> > >
> > >
> > > On Wed, 2005-05-11 at 12:32 +0800, Shayne O'Neill wrote:
> > > > I'm having a rather odd problem with one of my 2 email accts. I'm a
> > > > dedicated pine user. I prefer the simpleminded efficiency of the system
> > > > over the glitz and glitter of gui clients. Plus I can be guaranteed I'll
> > > > never have to view "horse porn" pictures or any of the other spammy crap
> > > > that evaids spamassassin from time to time.
> > > >
> > > > However one of my inboxes just locks up.
> > > >
> > > > At first I thought it might of been too full. There was a couple of
> > > > thousand mails in there (never a problem on the guild server, where 30,000
> > > > mails in the inbox barely raises an eyelid from the server). So I copied
> > > > the mail out via the fs into a folder and start up pine. Beautiful pine
> > > > starts, although there is no way in hell it'll open that inbox.
> > > >
> > > > A few days later however, at just over 100 emails, the new clean inbox
> > > > won't open.
> > > >
> > > > I dont think its file. And I dont think its memory. We recently upgraded
> > > > the memory on the server, and it was coping with magnitudes larger inboxes
> > > > pre to that.
> > > >
> > > > Any idea where I should be looking?
> > > >
> > > > Shayne;.
> > > >
> > > > --
> > > >  I wish a robot would get elected president. That way, when he came to
> > > > town, we could all take a shot at him and not feel too bad.
> > > > - Jack Handey (And now, Deep thoughts)
> > > > _______________________________________________
> > > > PLUG discussion list: plug at plug.org.au
> > > > http://www.plug.org.au/mailman/listinfo/plug
> > > > Committee e-mail: committee at plug.linux.org.au
> > > >
> > >
> > > _______________________________________________
> > > PLUG discussion list: plug at plug.org.au
> > > http://www.plug.org.au/mailman/listinfo/plug
> > > Committee e-mail: committee at plug.linux.org.au
> > >
> > _______________________________________________
> > PLUG discussion list: plug at plug.org.au
> > http://www.plug.org.au/mailman/listinfo/plug
> > Committee e-mail: committee at plug.linux.org.au
> >
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://www.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
>



More information about the plug mailing list