-
-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipes instead of command line and random locks #152
Comments
could you please provide a link |
Hi neurobin, |
you just need to fork this repository, then apply your patches, then push. After that you can go to https://github.com/neurobin/shc/pulls to create a PR. |
Done. I hope it will be useful. |
Just find out I implemented almost the same idea as this solution, except the anoymous pipe / fifo difference. |
Hi all,
I suggest a solution (at least in my experience), for a couple of questions appearing among the Issues.
Sorry, I'm not familiar with the mechanism of pull request and so on, but all the stuff is simple enough to be manageable by a simple:
patch shc.c shc.patch
againt the current master branch, where shc.patch is extracted from:
shcpatch.zip
A drawback of the "pipe" feature, is the fact that the script may lose the possibility to retrieve the original name by accessing
$0, $ARGV[0]
orsys.argv[0]
(depending on the language). Often this can be worked around referring to the $_ environment variable, but not always. In exchange for this annoyance, the limit on the script size and the possibility of seeing the source in clear withps
or/proc/*/cmdline
both disappear.The patch has been applied to the "original" v3, and has been working reliably for years under linux. Only recently I discovered this git repo with the updated version.
The text was updated successfully, but these errors were encountered: