should "kill --list" actually work on my f20 system? [NEVER MIND]

[g]

On 03/01/14 17:51, Robert P. J. Day wrote:
> On Sat, 1 Mar 2014, Robert P. J. Day wrote:
>
>>
>>    first time i noticed this -- was demonstrating the "kill" command in
>> a training course this week, showed "kill -l", had students check man
>> page for "kill" which suggested that "kill --list" should also work,
>> but:
>>
>> $ kill --list
>> bash: kill: -list: invalid signal specification
>> $
>>
>>    am i doing something wrong? man page also suggests:
>>
>>    -L, --table
>>          Similar  to  -l,  but  will print signal names and their corresponding
>>          numbers.
>>
>>    but:
>>
>> $ kill -L
>> bash: kill: L: invalid signal specification
>> $
>>
>>    should those work? am i missing something? is it a bug?
>
>    argh ... just noticed that, by default, "kill" is a shell builtin so
> i'm getting the builtin rather than the command.
>
> rday

as a work around, from years back, to save having to type in
command path, is to add an alias to .bashrc;

    alias ckill='/bin/kill'

then you only have to remember differance of the 2. :-)

also, when you get an error on issuing any command, note if
error message starts with 'bash:' or just command's name.

also be aware that there is more than just 'kill' to terminate
a process;

    ]$ locate kill|grep man/man

-- 

peace out.

in a world with out fences, who needs gates.

tc.hago.

g
.