I have installed a couple times (works great BTW) using the ./install script.
The first run after install always start with file permission errors (particularly in the logs) directory. I overcome this by chmod'ing them but I'm wondering if the script is missing a permissions step?
Just tyring to be helpful as I've noticed it on a couple fresh installs now.
I have installed a couple times (works great BTW) using the ./install script.
The first run after install always start with file permission errors (particularly in the logs) directory. I overcome this by chmod'ing them but I'm wondering if the script is missing a permissions step?
Just tyring to be helpful as I've noticed it on a couple fresh installs now.
<!-- github-sync-id:2895382050 -->
After installing with the .install script, i needed to chown the logs dir to my default user:group and change the user and group in the .service file to use the default user:group to get the service to run without errors.
After installing with the .install script, i needed to chown the logs dir to my default user:group and change the user and group in the .service file to use the default user:group to get the service to run without errors.
<!-- github-comment-id:2794651778 -->
After installing with the .install script, i needed to chown the logs dir to my default user:group and change the user and group in the .service file to use the default user:group to get the service to run without errors.
Was the user not the one running the script or the scripted mesh-bot? I assume?
> After installing with the .install script, i needed to chown the logs dir to my default user:group and change the user and group in the .service file to use the default user:group to get the service to run without errors.
Was the user not the one running the script or the scripted mesh-bot? I assume?
<!-- github-comment-id:2794688772 -->
That user ran the script was the default user. Interesting I also had to change after= in the .service to After=multi-user.target in order to not get an error on reboot
That user ran the script was the default user. Interesting I also had to change after= in the .service to After=multi-user.target in order to not get an error on reboot
<!-- github-comment-id:2794753118 -->
That user ran the script was the default user. Interesting I also had to change after= in the .service to After=multi-user.target in order to not get an error on reboot
What's your OS?
> That user ran the script was the default user. Interesting I also had to change after= in the .service to After=multi-user.target in order to not get an error on reboot
What's your OS?
<!-- github-comment-id:2794944355 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I have installed a couple times (works great BTW) using the ./install script.
The first run after install always start with file permission errors (particularly in the logs) directory. I overcome this by chmod'ing them but I'm wondering if the script is missing a permissions step?
Just tyring to be helpful as I've noticed it on a couple fresh installs now.
Yea what's the error or change needed? I have been trying to track this and haven't found it yet
After installing with the .install script, i needed to chown the logs dir to my default user:group and change the user and group in the .service file to use the default user:group to get the service to run without errors.
Was the user not the one running the script or the scripted mesh-bot? I assume?
That user ran the script was the default user. Interesting I also had to change after= in the .service to After=multi-user.target in order to not get an error on reboot
What's your OS?
pushed a change which should fix the problem I think
raspbian bookworm
this should be resolved now