We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
adduser fab
adduser fab tty
adduser fab sudo
sudo python setup.py install
~/OctoPrint/scripts/octoprint.default
cd ~
sudo cp OctoPrint/scripts/octoprint.init /etc/init.d/octoprint
sudo chmod +x /etc/init.d/octoprint
sudo cp OctoPrint/scripts/octoprint.default /etc/default/octoprint
sudo update-rc.d octoprint defaults
sudo service octoprint start
sudo service octoprint status
The init.d script should successfully start OctoPrint.
The init.d script barfed because it couldn't figure out how to call "log_warning_msg" (because the line which includes it is below the call).
1.3.0 tag
Yes, I have read the FAQ.
The text was updated successfully, but these errors were encountered:
Thanks for the PR, merged on both maintenance and devel. Will be part of the 1.3.1 release.
maintenance
devel
Sorry, something went wrong.
Part of 1.3.1 which has just been released.
No branches or pull requests
Reprodutcion steps:
adduser fab
adduser fab tty
adduser fab sudo
sudo python setup.py install
~/OctoPrint/scripts/octoprint.default
so that the user is "fab" instead of "pi"cd ~
sudo cp OctoPrint/scripts/octoprint.init /etc/init.d/octoprint
sudo chmod +x /etc/init.d/octoprint
sudo cp OctoPrint/scripts/octoprint.default /etc/default/octoprint
sudo update-rc.d octoprint defaults
sudo service octoprint start
sudo service octoprint status
Expected behaviour
The init.d script should successfully start OctoPrint.
What happened instead?
The init.d script barfed because it couldn't figure out how to call "log_warning_msg" (because the line which includes it is below the call).
Branch & Commit or Version of OctoPrint
1.3.0 tag
Yes, I have read the FAQ.
The text was updated successfully, but these errors were encountered: