Just encountered this bug as well. Here are my two eurocents: The fact that '/bin/kill -L' *does* work as documented in 'man 1 kill' but 'kill' (ie. bash built-in kill) *does not* is an inconsistency. Inconsistencies should be avoided. IMHO this could be fixed EITHER by:
- removing the 'kill -L' info from the 'man 1 kill' manpage *AND* removing the 'kill -L' functionality from /bin/kill OR by - implementing the 'kill -L' functionality in bash *AND* adding the 'kill -L' info to the 'SHELL BUILTIN COMMANDS' section of the 'man 1 bash' manpage. I do realise that technically the present state of affairs is not a bug, and technically both (bash built-in) 'kill' and '/bin/kill' work as documented on their respective manpages. However, I feel that the different behaviour of '/bin/kill' and 'kill' still constitutes an inconsistency that is likely to entrap unwary users. I feel that not fixing this inconsistency on the aforesaid technical grounds would be a lame copout and not quite in tune with the philosophy and mission of Ubuntu Linux (or GNU/Linux. Whatever.). As an aside, am I the only guy who finds that bash(1) monster manpage thoroughly inconvenient, and who finds it difficult to grep the correct part of that page when looking for documentation of a specific built-in command? All that said, I can't code, and you're under no obligation to do as I wish. If you like the above and want to do something about it, great. If not, that's also quite fine. Your call. -- kill -L does not work https://bugs.launchpad.net/bugs/23647 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs