- Returns exit code 0 if no processes were killed (unlike -q)
Uh…why? If you want to ignore the exit status, just ignore it.
Name:
Anonymous2008-05-25 14:26
Well, I need it to return non-zero *only if* if there was a problem killing it (ignoring SIGTERM, etc.), *not* if it just couldn't find anything to kill.
>>4 google UNIX Programmer's Manual or UNIX System Administrator's Manual
Name:
Anonymous2008-05-25 14:39
This is retarded, gb2lulznix.
>>6
Return values are not only "zero and non-zero". i.e. you can use 1 for general errors, 2 for no process killed, 3 for problems killing.
Name:
Anonymous2008-05-25 23:38
>>7
Only thing is, shell scripts consider return code 0 successful and anything nonzero as a failure.
But I could do that, only problem is it would break any existing script that depends on killall to only return 0 or 1.
So I think my idea is better.
Name:
Anonymous2008-05-25 23:53
>>8
Anyway, consider yourself lucky if you can get that as a GNU extension[1] in coreutils that will get released next year. I mean, it will work only in your computer.
[1]I'm 99% sure it will get rejected. It's 2008, everything has been written already and you can't add extensions anymore.
Name:
Anonymous2008-05-25 23:57
Only thing is, shell scripts consider return code 0 successful and anything nonzero as a failure.
That if you use "boolean chains", which is purely sintactic sugar. Do you think that breaking portability and patching/recompiling one of the coreutils is better than adding two lines to your script?
Disregard that, I'm so EXCITED I posted it in the wrong thread.
Name:
Anonymous2008-05-26 9:11
>>9
Don't care if it gets rejected. I'll release and maintain my own version then. A Better Way To KillAll(1)®
>>10
Of course I don't want to break existing compatibility. That's why I want to make it so it only does this when I specify a -Q switch (different from -q btw).
-e,--exact require exact match for very long names
-I,--ignore-case case insensitive process name match
-g,--process-group kill process group instead of process
-i,--interactive ask for confirmation before killing
-l,--list list all known signal names
-q,--quiet don't print complaints
-r,--regexp interpret NAME as an extended regular expression
-s,--signal SIGNAL send this signal instead of SIGTERM
-u,--user USER kill only process(es) running as USER
-v,--verbose report if the signal was successfully sent
-V,--version display version information
-w,--wait wait for processes to die
>>42
Umm... global cooling is a much more important problem than global warming. Did you for example know that the amount of sunlight that gets to the surface of the earth has decreased by 50% since the 50s?
Name:
Anonymous2008-05-31 12:13
>>47
That's global shading, and it means that global warming is a way bigger problem, because it's being masked by global shading.
Anyone have that link to the openbsd mailing list when theo said "The ports system has no non-free material, its just a collection of links"?
>>48 That's global shading, and it means that global warming is a way bigger problem, because it's being masked by global shading.
That depends on how you look at it...
Name:
Anonymous2009-03-06 6:15
The same node twice I mentioned shoving a tree on a queue because recursion naturally fits best on a 2GHz core 2.
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy