jhell DataIX.net> writes:
[snip]
>
> Now pkill -v sleep on my system actually causes my Xserver to exit with a
> unexpected signal 15.
Yes. "pkill -v sleep" kills all your own processes except for sleep. As root,
it kills all processes running on your machine except for sleep.
-V is not a go
Jason Spiro gmail.com> writes:
[snip]
>
> You could rename killall to something else, and update the manpage to show the
> new name, then symlink or hard link "killall" to the new name forever. This
> would encourage people to use the new name, but it would never forc
Xin LI delphij.net> writes:
> killall is used for instance, shutdown scripts. Yes you get the warning
> message on your console but not the remote ssh.
[snip]
> It's way too late to say something a "mistake" after about 15 years.
[snip]
> FreeBSD users are already get used
> with our killall b
Xin LI delphij.net> writes:
> killall can be used by scripts which just works in the past, and will
> never notice the warnings.
On what scripts will nobody notice the warnings? For example, AFAIK, cron job
output is always mailed to root. The only scripts I can think of are scripts
called by
jhell DataIX.net> writes:
>
> This is what shell aliases are for and what a system admins job consist
> of. If it gives you that much of a problem just alias it out for your self
> in your .cshrc .shrc .bashrc .bash_profile etc. If you want to change
> something on a more per user basis figure
Daniel O'Connor gsoft.com.au> writes:
>
> Why not get Sun and HP to change killall to match Linux & *BSD
> behaviour?
>
>
> Although seriously, why not? killall just killing everything is a fairly
> dangerous command with almost no use in the real world.
Because I find that when I send feed
Craig Small enc.com.au> writes:
> On Tue, Dec 22, 2009 at 01:31:02AM -0500, Jason A. Spiro wrote:
>
> Hello Jason (and the FreeBSD folk),
>
> The problem for me is that killall in Linux has been called that for a
> very long time now. psmisc came out 11 years ago and before that killall
> was i
Gary Jennejohn freenet.de> writes:
> I'm wondering why we even need killall when pkill seems to have the same
> basic functionality and is located in /bin (and /rescue) rather than /usr/bin?
I like killall because of its -v (verbose) option. It lets me know what killall
killed. You just inspir
jhell DataIX.net> writes:
[snip]
> PS: Applying your changes to a mailing list are not const.
What does that sentence mean?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send
9 matches
Mail list logo
