Linux

The 203 error you got is because your script isnt a valid executable, it needs to have a shebang at the top, you can change it to something like this and set the executable bit with chmod +x <file>

#!/usr/bin/env bash
google-drive-ocamlfuse ~/googledrive

this tells it to run using bash as the interpreter.

Im not familliar with this google drive software, but im figuring that its exiting with an error code cuz its running as a system service, and $HOME probobly isnt set so ~ doesnt expand and the software gets an invalid path.

But I recommend using a user service for this, it will run when you login, you should be able to copy the service file you already have into ~/.config/systemd/user/ and run systemctl --user daemon-reload and systemctl --user enable startup.service --now, this will enable and start the service in one go.

I also recommend adding the following lines under [Service]

Type=simple
Restart=always
RestartSec=60

idk if the software will exit if it loses network or wifi or anything, but this will have it automatically restart after 60 seconds, should it exit for any reason.

If you need it to run before login, it is possible to do with a system service, but it will need a bit more setup

I would just throw google-drive-ocamlfuse ~/googledrive in your .profile, but if you want to use systemd:

[Unit]
Description=Google drive fuse mount
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=<USER>
ExecStart=/usr/bin/google-drive-ocamlfuse /home/<USER>/googledrive
ExecStop=/usr/bin/google-drive-ocamlfuse -u /home/<USER>/googledrive

[Install]
WantedBy=multi-user.target

I had an idea of trying to use fstab to make it mount the same way as any other drive, which lead me to this page:

https://github.com/astrada/google-drive-ocamlfuse/wiki/Automounting#mount-using-fstab

Hopefully you can find some clues in there.

i would install cron if its not installed, then add a file under

/etc/cron.d/someNiceToRememberName

and with an editor write the following in it:

@reboot root /bin/bash -x /usr/local/bin/ocamlfuseStartup.sh >> /tmp/output 2>&1 ; echo returncode=$? >> /tmp/output

where root is the user it should run with and the redirection (>> /tmp/output 2>&1) is for seeing what is wrong, and echo returncode= prints the exit error indicator.

you might be able to do this with systemd too, but it often messes things up and i like i.e. clean log outputs.

for testing you can add a line that would start it without a reboot.

22 * * * * root /path/to/your/command parameters >> /tmp/output 2>&1

where the 22 is the next minute it should run. with this cronjob it would be run at every x:22 after each hour 09:22 pm 10:22 pm aso. i do this sometimes for testing

as systemd starts cron with a broken environment too, it might as well not work using cron, but then you know its the broken environment systemd starts it with. if thats your problem, you might want to add: PATH=$PATH:/usr/sbin:/usr/local/sbin

somewhere at the top of the shellscript depending on what is missing, which by itself would be the directories the commands executed are in. in terminal use :

$ which sed
/sbin/sed

for example to find where the "sed" binary is located (if the script cannot find it) you could change every occurance of "sed" in the script with the full path to it, or add the directory using the PATH variable as a colon separated list of directories to search commands in (where order matters)

to maybe more easy see what is missing i added the -x as a parameter to bash which makes it print out a line for every command it executes to sdterr so you can see what the last commands were. you can try it in the terminal (if your terminal is bash or compatible

$ set -x
$ echo foo
+ echo foo
foo
$ 

i'ld guess systemd starts the shellscript with a broken environment and thats maybe why it doesnt work, maybe try adding this to the script too:

echo PATH: $PATH

somewhere at the top of the script and use the redirection i showed for the cron job. run it once in your terminal and compare the output with what it prints during automated script run.

good luck.

transition to linux. One of the first things I have hit a wall on is getting a file to execute on boot using systemd.

I am trying to use this package to be

that bash thing is the interpreter. the script ocamlFuseStartup.sh is written as bash (possibly the same as your terminal) if that script has a "shebang" (#!/bin/bash) as the very first line AND the file has the execute permission set (chmod +x /path/to/file), then you dont need /bin/bash at the beginning to start it.