On Tue, Oct 11, 2011 at 2:33 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 11.10.2011 23:04, schrieb Canek Peláez Valdés: > > [...] > >> systemctl status ssd-thingies.service >> >> If everything went OK, it should have a line like this: >> >> Process: 1234 ExecStart=/my/path/to/ssd-thingies (code=exited, >> status=0/SUCCESS) >> >> Regards. > > Thanks for the explanation! > > I tried it right now, unfortunately I get: > > # systemctl status ssd-thingies.service > ssd-thingies.service - SSD thingies > Loaded: loaded (/etc/systemd/system/ssd-thingies.service) > Active: failed since Tue, 11 Oct 2011 23:28:05 +0200; 21s ago > Process: 6696 ExecStart=/etc/local.d/stefan.start (code=exited, > status=203/EXEC) > CGroup: name=systemd:/system/ssd-thingies.service > > Is it a permission-issue? AFAIK systemd runs w/ root?
It runs as root, but it's already telling you the problem: > Process: 6696 ExecStart=/etc/local.d/stefan.start (code=exited, > status=203/EXEC) Your script (I believe) does not have execution perms. All the commands for ExecStart (and ExecStop) need to be executable, so do a chmod +x /etc/local.d/stefan.start Also, if your scripts does not return 0 (or the last command it executes does not return 0), it will tell you with the status= flag. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
