On Wed, 3 Feb 2010 16:17, eitanadlerlist@ wrote:
Yeah - I wasn't sure what else to use.
Does the -V work as intended? Is this a worthwhile patch?
IMHO the biggest problem with unix system commands is the lack of constancy
of the flags.
Personally I would like to see pkill have this option as '-l' since pgrep
uses '-l' for long output I think it would make more sense if the user is
already used to what they expect to find in pgrep be also available in
pkill.
Other than that it works as expected. ;)
On Wed, Feb 3, 2010 at 7:58 PM, jhell <jh...@dataix.net> wrote:
On Wed, 3 Feb 2010 12:52, jhell@ wrote:
On Wed, 3 Feb 2010 10:00, eitanadlerlist@ wrote:
I added an option to pkill which lists what processes it kills and what
signal is sent. If no signals are sent it prints out the same message
killall does.
Unfortunately that patch works but has unintended operation that can be
seen with the following.
sleep 1000 &
pkill sleep
No matching processes belonging to you were found
[1]+ Terminated: 15 sleep 10000
It then kills sleep and still prints no processes belong to you message.
Now pkill -v sleep on my system actually causes my Xserver to exit with a
unexpected signal 15.
Without the patches it works as it should...
Overhead endured.
Ugh! ignore the pkill -v comment. Should have noticed the -V instead.
--
jhell
--
jhell
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
