On 2012-01-27, Harry Putnam wrote:
>
> When `aptitude remove' leaves the nasty bugger behind what is the
> procedure to finally be clear rid of it?
>
You must have some kind of script that's hung, no?.
Whiptail is light as the wind.
If a script using whiptail is a "hung" process, getting rid of
Harry Putnam wrote:
> Bob Proulx writes:
> >> None the less, whiptail is still here hogging away at 75-80 percent
> >> cpu.
> >>
> >> When `aptitude remove' leaves the nasty bugger behind what is the
> >> procedure to finally be clear rid of it?
> >
> > # pkill whiptail
>
> Well, yes. I know ho
Bob Proulx writes:
>> None the less, whiptail is still here hogging away at 75-80 percent
>> cpu.
>>
>> When `aptitude remove' leaves the nasty bugger behind what is the
>> procedure to finally be clear rid of it?
>
> # apt-get install procps
>
> # pkill whiptail
>
> Or use 'killall' if you
Harry Putnam wrote:
> I notice whiptail hogging cpu and decided to get rid of it and return
> to the package it is replacing `dialog'.
If whiptail (or dialog) is hogging cpu then it is probably off in the
weeds and should be killed. It is simply a small interactive dialog
for scripts and is used
Running Wheezy and kde plasma desktop
I notice whiptail hogging cpu and decided to get rid of it and return
to the package it is replacing `dialog'.
aptitude remove whiptail... offers a few decisions, and I made the ones
that replace whiptail with dialog.
None the less, whiptail is still here ho
5 matches
Mail list logo
