) than it being removed.
>
>
> $ sleep 50 &
> [1] 2673
> $ pgrep -fl sleep
> 25664 sleep 5
> 2673 sleep 50
> $ pgrep -fl 'sleep 50'
> 2673 sleep 50
> $ pkill -l 'sleep 50'
> $ pgrep -fl 'sleep 50'
> 2673 sleep 50
> $ #fuck
&g
s tightly coupled as they
are, I think allowing -l for both is helpful.
I agree the output is inconstistant, but I'd rather have that fixed (if
possible) than it being removed.
$ sleep 50 &
[1] 2673
$ pgrep -fl sleep
25664 sleep 5
2673 sleep 50
$ pgrep -fl 'sleep 50'
267
I don't think the -l flag to pkill is useful. It's behavior is oddly
different from pgrep -l (and more different with pgrep/pkill -f). Or
rather, it's not just long output, but also turns on verbose mode when
otherwise nothing would be printed. The only use case I can think of
is "did I kill the ri