On 01.03.2014 19:11, Robert P. J. Day wrote:
On Sat, 1 Mar 2014, Joachim Backes wrote:
> On 03/01/2014 01:06 PM, poma wrote:
>> On 01.03.2014 12: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
>>>
>>
>> Yep! :)
>>
>> $ type kill
>> $ type $(which kill)
>> $ builtin kill
>> $ builtin $(which kill)
>> $ $(which kill) -L
>> $ man 1 builtins
oh, once i twigged on what was happening, i was fine; i just can't
believe i'd never noticed it all these years. always a learning
experience ...
rday
Due to gazillions of data, in fact it is to be expected. :)
poma
I've been working so hard
I'm punching my card
Eight hours for what?
Oh, tell me what I got