Ron Johnson posted on Thu, 03 Nov 2011 18:28:23 -0500 as excerpted:
> On 11/03/2011 05:47 PM, Duncan wrote:
>> Ron Johnson posted on Thu, 03 Nov 2011 17:34:09 -0500 as excerpted:
>>
>>> Anyway... "Task Manager" (Real Men run top(1) in a separate window...)
>>> just reports what the kernel tells it
On 11/03/2011 05:47 PM, Duncan wrote:
Ron Johnson posted on Thu, 03 Nov 2011 17:34:09 -0500 as excerpted:
Anyway... "Task Manager" (Real Men run top(1) in a separate window...)
just reports what the kernel tells it.
I parsed his "task manager" reference as to pan's TM, not the one in his
DE,
Ron Johnson posted on Thu, 03 Nov 2011 17:34:09 -0500 as excerpted:
> Anyway... "Task Manager" (Real Men run top(1) in a separate window...)
> just reports what the kernel tells it.
I parsed his "task manager" reference as to pan's TM, not the one in his
DE, corresponding to top, etc.
Meanwhile
I've used "pan --no-gui --nzb ${FOO}.nzb -o ." on *many* occasions and
it always returns to the $ prompt when d/l is complete. Using v0.135.
If you want something to run only if a process errors out, then use
"||". For example:
$ pan --no-gui --nzb ${FOO}.nzb -o . || dem
Anyway... "Task
Graham Lawrence posted on Thu, 03 Nov 2011 08:17:44 -0700 as excerpted:
> Duncan, thank you for pointing out that && is a conditional test. I had
> understood && simply as "wait until previous instruction completes
> before proceeding", because that is the question I sought to answer when
> I fir
Duncan, thank you for pointing out that && is a conditional test. I
had understood && simply as "wait until previous instruction completes
before proceeding", because that is the question I sought to answer
when I first came across it via google; hence my seemingly
contradictory logic. If pan fai
