263 reputation
37
bio website
location
age
visits member for 2 years, 4 months
seen Nov 16 at 23:35

Mar
18
comment Rsync filter: copying one pattern only
Please read carefully. No need to feel offended. I just wanted to contribute for the common good. Hope this helps someone.
Mar
18
comment Rsync filter: copying one pattern only
I am merely reporting: In my environment your suggested order fails whereas that of @jmanning2k works plus he also explains the reasons (greediness behavior).
Mar
17
awarded  Commentator
Mar
17
comment Rsync filter: copying one pattern only
Hint appreciated, but your filter order fails me! At least in my environment (rsync 3.0.9 on Mac OS X 10.6.8). As of 2014-03-17 @jmanning2k has the best answer, as it solves the original posters inquiry exactly, reproducible within my environment!
Mar
17
comment Rsync filter: copying one pattern only
As of 2014-03-17 this is the best answer, as it solves the original posters question exactly. Please vote it up! If you add --prune-empty-dirs (or shortcut -m) you even spare yourself many empty directories at the destination, except of course you want them as a reminder or structural blueprint.
Jan
13
awarded  Notable Question
Jul
16
awarded  Yearling
Oct
5
awarded  Popular Question
Aug
8
awarded  Good Question
Jul
24
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
Am still in the process of testing. Also updated my question with the section Practical purpose / application. Now I realize that even if the timestamp-generator is precisely timed, the later parts in the pipe (tee and nc) also consume their time. I need to consider this too! How would I do this in the solutions: watch --precise, Perl Time::HiRes, shell threading/background ?
Jul
24
awarded  Editor
Jul
24
accepted Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
Jul
24
revised Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
added 582 characters in body
Jul
24
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
If you run it with 0.01 sec or 0.001 sec intervals, it is just a matter of a few seconds or less until the program aborts with the "negative time" error. But for my purpose it fits!
Jul
24
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
I ran it overnight with no other active user applications with an interval of 1 sec, and it ran for 29241 secs, without a single skipped second! This will fit my purpose. Then I ran it again this morning with an interval of 0.1 sec, GNU date with +%N and after only 3 min it threw that error: Time::HiRes::sleep(-0.00615549): negative time not invented yet at ~/bin/repeat.pl line 23. Line 23 in my saved script: sleep $start - time();
Jul
23
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
I guess you meant the same like @lynxlynxlynx
Jul
23
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
Wow, I am very curious to test that particular patched watch version. I downloaded the source code via fink. Then cp-ed the tarball to its own dir. Added your patch file. ran patch. But some hunks failed to be patched. Usually I first run patch, then make install. But I fear to compile and install all that other procps stuff, which may interfere with my OSX 10.6 intallation. How to I configure the source and then compile watch alone?
Jul
23
comment Run unix command precisely at very short intervals WITHOUT accumulating time lag over time
@tylerl: How would the concrete command line look like for your solution?
Jul
20
comment Detect file-type with the help of magic-file and rename file-suffix accordingly
Btw, my original problem was solved, as there is a software, which reorganises that bunch of flat UID-named suffix-less files into a proper folder structure with proper filenames with suffixes. iPhone Backup Extractor (supercrazyawesome.com). Nevertheless it would be good to know how to automatically add file suffixes according to detected filetype of files without a file-suffix in their file-name.
Jul
20
comment Detect file-type with the help of magic-file and rename file-suffix accordingly
I had hoped that the magic DB itself contains such a mapping of mime/file-types to file suffixes, and that there's a ready-made solution for this. Still, thanks a lot for your approach.