Joe Zeff wrote:
>
>I have, several times, caused problems by accidentally starting Pan
>twice without realizing it. (Mostly, the program gets tangled up about
>which articles have been read until I edit the newsrec file.) I'd like
>to suggest that Pan create a file, pan.lok, in its own direct
Duncan <1i5t5.dun...@cox.net> wrote:
>
>Depending on your "brand" of "unix", "killall" will likely work better
>for you. It'll allow you to avoid all that grepping for the pid, etc.
>You could also avoid the "if" logic that way. If pan's running, it'll
>kill it, if not, no harm done. Also, at
On 10/13/2009 Alan Meyer wrote:
That seems safer to me than killing a process you had forgotten
was running or, if on a multi-user system, a process that another
user was running.
I have, several times, caused problems by accidentally starting Pan
twice without realizing it. (Mostly, the prog
> > ... echo Pan is already running, stopping it first ...
Another reasonable solution to the pan-is-running problem
might be to terminate, not pan, but the nzb download script,
for example with a message like:
"Please close pan before attempting to download from nzb."
That seems safer to me
Jan-Jaap Bakker posted on Tue, 13 Oct 2009 03:10:00 +0200 as excerpted:
> if [ "$PANPID" != "" ]
> then
> echo Pan is allready running, stopping it first...
> kill -15
> $PANPID
> #this soft kill allows pan to save the current tasks.
> else
Depending on your "bra
