-
Notifications
You must be signed in to change notification settings - Fork 79
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
Exception running megafuse #57
Comments
FWIW, I'm having a similar issue, also with -f -o allow_other -o uid=1000. When I become root via sudo or su, I don't get the above error (sometimes I get a Segmentation fault, though). However, sometimes it works. It always gets the above error when run as a daemon (monit runs a script that invokes MegaFuse if needed). @junalmeida Did you ever find a fix for this? |
Steps to reproduce:
The env line re-creates the shell environment typically available to daemons. |
After comparing two shell environments - one where the above error happens 100% of the time and one where it happens 0% of the time - I found a workaround. If you add HOME to your shell's environment, this error goes away. Put this line before any MegaFuse invocation:
Without looking at the source code, I'd guess that something involved in processing the fuse parameters requires knowing what |
My upstartjob:
The text was updated successfully, but these errors were encountered: