455 reputation
210
bio website
location
age
visits member for 1 year, 10 months
seen Jul 16 at 18:17

Jul
2
awarded  Curious
Jun
19
comment break out of find if an -exec fails
@savanto this does seem to work - if you provide that as an answer, I'll accept it.
Jun
9
awarded  Caucus
Jun
6
comment break out of find if an -exec fails
It's not working for the case above. After find . -iname \*.java -exec sh -c 'javac "${0}" || kill '$$ {} \; file A.java fails and, still, file B.java gets compiled.
Jun
5
revised break out of find if an -exec fails
added 89 characters in body
Jun
5
comment break out of find if an -exec fails
find . -iname \*.java -exec javac {} \; -o -quit, too, fails to process any files. Strangely, find . -iname \* -exec echo 'foo' \; -o -quit does "process" the files.
Jun
5
comment break out of find if an -exec fails
I seem to have trouble making it clear where the exec stops and the -o starts. Both find . -iname \*.java -exec javac {} -o -quit \; and find . -iname \*.java -exec javac {} \; -o -quit \; fail (in different ways)
Jun
5
asked break out of find if an -exec fails
May
30
comment Emacs: Deleting a line without sending it to the kill ring
what exactly is (control shift ?k) ? I copied the line verbatim in my .emacs file and tried using the CTRL+SHIFT+k keystroke and it didn't seem to work.
May
21
revised diff -r only for certain file types
added 208 characters in body
May
21
asked diff -r only for certain file types
Apr
24
accepted heuristically find how different a set of files are
Apr
24
comment heuristically find how different a set of files are
@WarrenYoung your point is valid for this particular use case. Still, such a quick-n-dirty heuristic would still be useful for this and other use cases.
Apr
24
comment heuristically find how different a set of files are
@Oli, yes plaintext files.
Apr
24
asked heuristically find how different a set of files are
Feb
19
accepted delete old log files except the last one (alphanumerically sorted)
Feb
19
asked delete old log files except the last one (alphanumerically sorted)
Feb
17
comment solution to rotate log files
Thanks but unless I 've missed something I prefer the solution with rotatelogs and a cronjob to delete old log files (which is the only part that rotatelogs doesn't provide out of the box). Seems like less configuration is needed (only a cronjob), I don't have to worry about sending signals or restarting processes (why should I?) and my scripts (except the cronjob) reside in the project's file system hierarchy meaning they are under git as well.
Feb
17
accepted solution to rotate log files
Feb
17
comment solution to rotate log files
OK so I guess rotatelogs with a size limit and a chronological timestamp coupled with a cronjob to delete old log files is exactly what I need since I won't have to worry about restarting processes, I am just logging stdout and expect rotatelogs to transparently switch to new files as I've seen it does.