According to Raider: While burning my CPU.
>
> Hi!
> I was getting my mail as usual (fetchmail/procmail). And there
> appears procmail:kernel-lock failed than procmail:kernel-unlock failed.
> What does this mean?
At a guess the programs cannot create a lock file or when they close cant
find the lock file causing the unlock problem.
Check the man pages and documentation for the programs concerned to find
out where the lock files are (supposed) to be created, check that the
directory exists and that a user application can write to that directory.
> So far I assume it's pine which is checking from time to time if
> there is new mail in /var/spool/mail/username. But I'm not sure. Also,
> this happened when one message was downloaded. Was that message
> delivered? I didn't checked the numbers (how many messages were at the
> end of delivery from which I'll substract the number of messages that were
> there already). I don't know if this will happen again... at least I
> never noticed it before.
>
> Raider
> --
> ``Liberate tu-temet ex inferis''
>
--
Regards Richard.
[EMAIL PROTECTED]
