120 reputation
7
bio website
location
age
visits member for 2 years, 7 months
seen Jul 30 at 17:30

vol7ron


About Me


Name:

While confusing to look at, it is not "Ron" as sometimes can be misinterpreted. It is actually a tribute to an inspirational cartoon of times past, Voltron.

Age:

If you ask, I might tell, but in the upper-20's lower-30's for a ballpark estimate.

Sports:

I like everything from FĂștbol to Football, but haven't been as enthused about the NBA, since Jordan. Their hearts just aren't in it.


Programming


Mainly driven by web scripting and relational database systems, but would really like to learn more about game design as well as core-level architecture.

Enthused Languages:

C++, Java, JavaScript, Perl, PHP, Python, Ruby, SQL|PL/SQL


Debates - Stance


MySQL vs PostgreSQL

PostgreSQL, especially 9.0, faster, stronger, and more importantly: more reliable.

PHP vs Perl

Depends on the language, but primarily Perl. Afterall, it was a Perl programmer that developed PHP only to use in addition to his Perl tasks, not as a replacement for it.

Apple vs Microsoft

Both. Competition drives the markets and will hopefully bring out the best in both. They both develop products to service their clients. Being a programmer, I prefer a MS or Linux based OS, preferably Red Hat or Ubuntu.


Jun
11
awarded  Popular Question
Apr
18
comment Best way to determine piped command to shell script?
Yes, I think you and Glenn Jackman are both correct. Thinking it wasn't possible was the first conclusion I came to, but I don't consider myself a Linux guru. I had hope that the Kernel might pass that information along in some way, so scripts could behave differently based on origination of STDIN -- logging was just one of the many potential uses.
Apr
17
comment Best way to determine piped command to shell script?
@glennjackman right. Exactly my line of thinking, which is why I'm looking for the best way. Preference would be not to quote. I'd rather sniff the shell history (if it's available at that point)
Apr
17
revised Best way to determine piped command to shell script?
edited tags
Apr
17
comment Best way to determine piped command to shell script?
print.sh will log the input, as well as format/output as part of a custom header
Apr
17
asked Best way to determine piped command to shell script?
Aug
13
awarded  Popular Question
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: then that makes sense (thank you), I was talking about the combination of them both, which I don't know how it'd work, but I imagine it could check the same file exponentially
Oct
25
awarded  Editor
Oct
25
revised Linux: Does find | xargs grep have limitations?
Fixed grammar
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: I think I misunderstood you. Were you talking about using grep as a standalone instead of piping find's output to it?
Oct
25
comment Linux: Does find | xargs grep have limitations?
that's a valid comment and I tried to answer it with I realize I wasn't specific on the path, but these are all well-named directories, not to be confused with any devices. It's still possible that a malformed filename with spaces could have split oddly - I'll have to check when I have a little more time; however I doubt it. I typically don't use spaces in Linux. I think in looking at the "errors" the stopping point was at different places, but like I said... I will check because I hate not knowing the cause of problems to prevent them in the future.
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Kevin: I'm not sure what that would buy me. find is supplying all the files, so grep shouldn't also need to read each file twice; unless, I'm not understanding the recursive nature of grep
Oct
25
comment Linux: Does find | xargs grep have limitations?
@Gilles: before I post a question, I try many options. In this particular instance it had no bearing on the outcome, so I included the version as part of the question
Oct
24
awarded  Commentator
Oct
24
comment Linux: Does find | xargs grep have limitations?
When I debugged, I removed the error redirection (removing the redirection of STDERR has no bearing on the result, or lack thereof) and I didn't notice anything other than permission denied/does not exist errors (no special characters). I think the does not exist errors were because of the spaces, but it encountered a few of those and still continued on. I'm still stumped on what the true nature was, but am appreciative of your help. I think I tried the -0 on xargs, but didn't do the -print0 on find -- thanks again!
Oct
24
comment Linux: Does find | xargs grep have limitations?
Your explanation makes sense. What I don't completely understand is why it would crash, and not continue on, even if it encountered a file that didn't exist. Regardless, this solved my particular issue +5 (if i could)
Oct
24
accepted Linux: Does find | xargs grep have limitations?
Oct
24
comment Linux: Does find | xargs grep have limitations?
@shellter I didn't see that, could you post a link
Oct
24
comment Linux: Does find | xargs grep have limitations?
@rici: I've removed both error redirections and the only errors that appear are Permission denied or No such file or directory, which I don't see applying to the path above. I've also tried -type f for the find to simplify the search