I have a BASH-script I want to run on start up.
My system is running systemd so I created a .service file with whith what I think is the neccessary information:
[Unit]
Description=My Script
After=network.target
[Service]
ExecStart=/home/myscript.sh
[Install]
WantedBy=multi-user.target
I used systemctl enable to 'register' it an rebooted.
On boot I was told my script would be executed, but I could neither see any of the messages ECHO should display on screen nor did it write something to a file, according to what I had written in the script. Additionally, It does not start the application it's supposed to start.
Systemctl status tells me that the script has run and exited successfully. Still, the script has no effect. If I run the script from a shell it works perfectly fine.
Do any of you know what could be my problem?
Best Answer
In addition to what TokyoMEWS found by themselves...
(which is not completely correct –
Type=forking
only becomes necessary if your script exits while its children are running)...other possible problems are:
I'm guessing that by "display on screen" you meant that the script simply writes something to stdout. This does not go to the screen during boot – rather, everything from a service's stdout is sent to the journal (or to syslog depending on your systemd version).
If you did actually attempt write to the screen (e.g. using
echo Hi >/dev/tty1
), then it's very likely that the script's output disappears when agetty clears the screen before showing login prompts. (To avoid that, you would have to order the unitAfter=getty@tty1.service
).To write something to a file, you need to have the file system mounted read-write. For this,
After=local-fs.target
might be necessary, otherwise the unit again might be started too early. But this depends on specific OS configuration.