-
Notifications
You must be signed in to change notification settings - Fork 5
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
Failed at step EXEC spawning #7
Comments
fix the Permission denied problem. something you did wrong. right now in a project very soon done, i will might check if it works on my machine. dont use feroda, but check the unit why is not giving permission for that shell script. |
Hi Patrik, it turned out that the systemd unit does a lot of confining for the service. In particular, it denied is access to user's home directories. Therefore, my solution was to copy the
I am fine with this workaround now. Maybe in future consider making this fix permanent. |
ok, i provide an option soon, right now sick, so it might take 1 2 weeks to implememt, thanks! |
Thank you. Feel better soon! |
did you do it using as a root user? it is intended to work with other than root. |
Dear Patrik,
First I would like to thank you for this great piece of software! Your RAMDisk is a savior. Recently I ran into an issue with starting the service. I use Fedora 35 with 5.15.14 kernel.
The output of the command
sudo p3x-ramdisk start petrstepanov
is following:Below I attach the listing of the
systemctl status p3x-ramdisk-petrstepanov.service
command:Also, the
journalctl -xeu p3x-ramdisk-petrstepanov.service
command provides following output:Things were working fine before. But probably after a recent system update the service is not starting anymore. So obviously the systemd cannot execute
p3x-ramdisk.sh
script located in the home folder. I ran into this post on StackExchange. It says the script has to be installed system-wide.Please let me know if you can provide any help here. Thank you again for the RAMDisk!
The text was updated successfully, but these errors were encountered: