Timeline for process files in a directory as they appear
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2018 at 8:57 | history | edited | Ole Tange | CC BY-SA 4.0 | added 14 characters in body |
| Mar 7, 2012 at 23:28 | vote | accept | J Jones | ||
| Mar 7, 2012 at 23:28 | comment | added | J Jones | Using inotify wait, and running a string of commands (as described here gnu.org/software/parallel/man.html#example__composed_commands ) was my final solution | |
| Mar 7, 2012 at 1:56 | comment | added | J Jones | After exploring what alerts get raised on it, i would agree, that it is just an open but empty file as data is being streamed into it. using CLOSE_WRITE was perfect for my situation. | |
| Mar 6, 2012 at 14:02 | comment | added | Ole Tange | The 'touch' is probably not a touch then: It is simply an open file with no content. Thus you can use the version above with no 'touch'. The key here is whether the file is closed and re-openend or if it stays open, and it most likely does the latter. | |
| Mar 6, 2012 at 13:59 | comment | added | Ole Tange | For more advanced quoting see: --shellquote, --quote, gnu.org/software/parallel/man.html#quoting | |
| Mar 6, 2012 at 2:46 | comment | added | J Jones | Answering my own comment, you can escape characters with a quoted (aka, out of parallel execution ). so my parallel looks like parallel ' awk '\''{ print $1 } '\''... | |
| Mar 5, 2012 at 3:37 | comment | added | J Jones | And my next comment would how can I use something like awk (needing to be escaped by single quotes) in a parallel statement where I want to send multiple commands (therefore needing to enclose the commands in single quotes as well, such as your top example. ........... Simple use case is: ls ~ | parallel ' du -k | awk '{ print $1 }';ls -l' | |
| Mar 5, 2012 at 1:08 | comment | added | J Jones | Ole, the touch actually comes from parallel it seems. I have parallel which operates on a list of files, changing their format and contents. However, it quickly runs through the inputs creating output files, and then slowly processes the inputs. (You can see my earlier process here: unix.stackexchange.com/questions/32162/… ) | |
| Mar 1, 2012 at 23:50 | history | edited | Ole Tange | CC BY-SA 3.0 | added 386 characters in body |
| Feb 29, 2012 at 13:50 | history | edited | Ole Tange | CC BY-SA 3.0 | added 58 characters in body |
| Feb 29, 2012 at 13:36 | history | answered | Ole Tange | CC BY-SA 3.0 |