New answers tagged upstart
The root cause was a change I did in fstab based on recommendations for solid state drives (SSD). I removed these lines and was able to reach the login screen with systemd: # ramdisks tmpfs /tmp tmpfs defaults 0 0 tmpfs /var/lock tmpfs defaults 0 0 tmpfs /var/log tmpfs defaults 0 0 tmpfs /var/run tmpfs defaults 0 0 tmpfs /var/tmp tmpfs defaults 0 0 My ...
EDIT with more details: My problem was incorrect device uuids in file /etc/fstab. (the red one is incorrect,the green one added by me and the red one is commented out) After correcting the uuids in /etc/fstab for / and swap (with infos from blkid), it works for me!
Could anyone adequately explain to a non-technical user how and if this affect us at all? In theory, this shouldn't affect the non-technical end user who doesn't get involved in the nitty gritty of how the system actually works. In practice, there are a lot of things that you're going to see. Here's an incomplete list: If you had add-on softwares ...
The headline news this week is that Ubuntu version 15.04 doesn't use upstart. It uses systemd. You can go back to upstart, which is a question all to itself; or you can write a systemd service unit for your service; or you can swipe an already-written one. There are plenty of already-written ones about. This mbpfan.service unit by Ismail Khatib has been ...
Layman users shouldn't notice any change, by design. It's an init system, not something users traditionally interact with. It should completely replace the functionality provided by Upstart —and do a few extra things— but the only time a non-technical user will see this is when it goes wrong. Users, sysadmins and developers who have been actively using and ...
The code below shows the upstart service configuration file /etc/init/nodemanager.conf. You execute the yarn-daemon.sh start nodemanager script as pre-start hook, and yarn-daemon.sh stop nodemanager as post-stop hook. This starts the actual nodemanager instance. The script checks if nodemanager is up. If nodemanager is down, the script exits. This signals ...
Probably there are some errors in you conf file. To verify it use: init-checkconf archiva.conf or initctl check-config archiva as described in upstart cookbook: 10.1.6.2 initctl check-config and 10.1.7 init-checkconf. Upstart use init daemon that, according to man page: On startup, the Upstart init(8) daemon reads its job configuration ...
Defining a variable in the /etc/init/scriptname.conf file in the form of NAME=value like you'd do in an initd script causes upstart to give this rather nonsense feedback (telling that there's a syntax error is much more suitable than saying that the script doesn't exist). Removing the line causes the script to be recognized and startable randomly (see my ...
Upstart uses inotify. If you drop a configuration file into /etc/init/, Upstart should detect and make the job available automatically. If you don't see it appear, there may be a problem in your new configuration. Try checking the logs for errors.
/etc/init is for system jobs - those services which are started independent of any user being logged in. These are typically system services. By default, commands are run as root unless setuid is used. ~/.config/upstart is for session jobs - these are run for a user logged into the GUI. What does your Upstart job do? Is it performing some function for ...
"Must run" depend on you needs. For example, I consider cron a must-have because otherwise I will not have log file rotation. And periodic updates check. But if you don't even want logs, and plan to check updates manually, your case is different. So basically the only correct answer is "it depends". Depends on how you want your system behave and on your ...
boot performance under systemd can be measured with the systemd-analyze plot tool. Realize that Ubuntu running systemd is very similar to Debian, which is very similar to every other GNU/Linux distro.
In my case it was an empty author field, like this: author "" It worked only after adding something in the quotes. # initctl reload-configuration was also throwing /etc/init/servicename.conf:2: Expected token to syslog instead of stdout. Too busy to file a bug report for a dying package.
This is an upstart issue. Go into your etc/init.d/ just change back to your old plexmediaserver script by removing the upstart linked version and renaming the backedup version of your plexmediaserver script.
Top 50 recent answers are included