Tag Info

New answers tagged


I had this problem also, gnome-session-Unity.log file was getting large. Before this I installed the scratch programming environment, this programm has the squeak-vm dependencies also installed 1st time on this machine. The squeak-vm was locked on the launcher, the line in the gnome-session-Unity log file (zenity:3190): GLib-WARNING **: ...


Ubuntu 14.04 uses Upstart only, but Upstart runs SysV init scripts, too. See /etc/init/rc*.conf for the Upstart jobs that are responsible for this. A lot of Ubuntu packages still use SysV init scripts to minimize the differences to Debian.


i know the question is about upstart, but just in case someone (like me) needs a init.d solution: replace the start_server() function in /etc/init.d/mongodb for the code below start_server() { test -e "$RUNDIR" || install -m 755 -o mongodb -g mongodb -d "$RUNDIR" NUMACTL=$(which numactl) if [ ! "$NUMACTL" ]; then # start original ...


… so either systemd is backwards compatible or all of them are running at once. This is why I find it confusing. The root of your confusion is that conclusion. It's wrong. The existence of directories in your filesystem does not imply that the subsystems associated with those directories are running. In fact, they do not all run ...


Now that systemd's the init system in Ubuntu, the table looks more like: +------------------+---------------+-------------------+---------------------------+-----------------------------------+ | | service | on a Mac | ...


I found that using net-device-up in /etc/init/xinitd.conf is actually the right approach, but by default, the event fires if any network device (including the loopback device) is ready. The full solution is to either specify that a specific network device needs to be up net-device-up IFACE=eth0 or that any network device other than localhost must be up ...


If for all the processes who wants to access session bus the same DBUS_SESSION_BUS_ADDRESS environment variable is set, you are going to have no problems (see the manual). But since upstart tasks are run in a "restrictive environment" you will not have access to that variable in a system job (e.g. those under /etc/init). However if you were to have it as a ...


Upstart by default will launch jobs in a very restrictive environment. My guess why it does this, for at least one reason, is that it can't assume you want to run the job as root, or any other given user. So it tries to be restrictive and secure by default. See: http://upstart.ubuntu.com/cookbook/#job-environment


The root does not have access to Xserver by default. In order to enable it, you need to copy your /home/sam/.Xauthority file to /root/.Xauthority sudo cp /home/sam/.Xauthority /root/ After the reboot simply enable the spacenavd daemon at the boot: sudo service spacenavd enable And start the spacenavd service: sudo service spacenavd start

Top 50 recent answers are included