Hi,
On Wed, Jul 18, 2012 at 3:14 PM, Noorul Islam K M wrote:
> Balachandran Sivakumar writes:
>
>> Hi,
>>
>>Bash shows it for me. kill -l in bash 4.1.x shows the same
>> output. But, when you say bash completion, were you trying kill
>> ? I don't think that shows it up. thanks
>
>
>
On Wed, 2012-07-18 at 15:14 +0530, Noorul Islam K M wrote:
> May be this one is customized by Debian or the OP might be using some
> *nix variant.
I heard some rumours that he uses BSD ;-)
--
regards
Kenneth Gonsalves
___
ILUGC Mailing List:
http://ww
Balachandran Sivakumar writes:
> Hi,
>
> On Wed, Jul 18, 2012 at 12:50 PM, Noorul Islam K M wrote:
>>
>> Which shell are you using? Bash completion is not displaying those
>> numbers.
>>
>
>Bash shows it for me. kill -l in bash 4.1.x shows the same
> output. But, when you say bash compl
Hi,
On Wed, Jul 18, 2012 at 12:50 PM, Noorul Islam K M wrote:
>
> Which shell are you using? Bash completion is not displaying those
> numbers.
>
Bash shows it for me. kill -l in bash 4.1.x shows the same
output. But, when you say bash completion, were you trying kill
? I don't think t
Girish Venkatachalam writes:
> kill is a word we normally use to mean murder. ;)
>
> In the UNIX world we often use it to destroy wayward processes.
>
> We also use it to send signals like SIGINFO.
>
> $ pkill -INFO dd
>
> $ kill -l
> 1HUP Hangup17 STOP Suspended (s
kill is a word we normally use to mean murder. ;)
In the UNIX world we often use it to destroy wayward processes.
We also use it to send signals like SIGINFO.
$ pkill -INFO dd
$ kill -l
1HUP Hangup17 STOP Suspended (signal)
2INT Interrupt
