Your skill will accomplish
what the force of many cannot
Re: Weird use warnings FATAL behaviorby naikonta (Curate)
|on Mar 18, 2008 at 09:19 UTC||Need Help??|
OK, here is the expanded version of the original OP's oneliner, following tye's explanation:
Run with correct command (just as comparisson):
No problem there. Now, run with no args (default command):
So I guess, it's the child that triggers the "Can't exec ..." warning that gets "upgraded" into fatal error (due to FATAL), trapped in $@, and dies. The child dies, the parent doesn't, that's HOW DID I GET HERE, I suppose. OTOH, if the no warnings; is uncommented, then well, no "Can't exec..." warning, no $@ trapping, and the child lives pretending nothing happens, yet covering up by asking HOW DID I GET HERE.
Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!