New answers tagged startup
Try adding Sleep into your script. Sleep 60 . /home/minecraft/multicraft/bin/multicraft -v start exit 0 Please increase the sleep time if above code does not work. Possible duplicate of "Startup Applications" not working
Work in progress This can be accomplished by using: a custom X session which starts a basic window manager and runs the script a custom configuration for LightDM which will autologin your user and use the above session a custom service for LightDM which will use the above configuration appropriate kernel parameters to disable the normal LightDM service ...
Could you try giving the full path to forever when you start it for rc.local. Might be that the $PATH isn't set as it is you when you're logged in. Failing that, is there some log that forever produces? Can you tee to output where you run the command, like: /usr/local/bin/forever start <full path to>/server.js | tee /tmp/forever-start.log
The answer is it's not true. You can't put an essential configuration control in /etc/network/interfaces despite the comments in the /etc/network/if-pre-up.d/bridge. Just do something ad-hoc.
As seen from the output of locate --regex '/etc/init(\.d)?/tomcat' tomcat7 is using the legacy SysV style init and hence the start/stop script is in /etc/init.d/. You can run the following command to remove all the symbolic links of /etc/init.d/tomcat7 in /etc/rc[0-6].d (or /etc/rcS.d) directories so that tomcat7 does not start automatically from next ...
Small update. Since 15.04, Ubuntu uses systemd instead of upstart by default so now to disable tor on startup we should run: sudo systemctl disable tor.service
Try this: sudo apt-get purge plymouth-theme-kubuntu-* sudo apt-get install --reinstall plymouth-theme-ubuntu-logo
I guess you've already solved the problem, but in case someone else comes across this thread, I recently had the very same issue and the solution was quite quick and simple all in all. After installing Debian in a new partition, booting Ubuntu took too long compared to before. So, I pressed E key on GRUB, removed the "quiet splash" option and pressed F10 ...
To run a (short-lived)1 command at startup using systemd, you can use a systemd unit of type OneShot. For example, create /etc/systemd/system/foo.service containing: [Unit] Description=Job that runs your user script [Install] WantedBy=multi-user.target [Service] Exec=/some/command Type=oneshot RemainAfterExit=yes Then run: sudo systemctl daemon-reload ...
Top 50 recent answers are included