Php server startup at boot

dr_nero · 4. August 2017

Hello everyone!

Thanks in advance for the help, and sorry for my approximate english.

In my OMV 2 machine, I have installed COPS server (http://blog.slucas.fr/en/oss/calibre-opds-php-server).
This php server starts with a command like this:
php -S 192.168.1.96:8080

Everything works wonderfully, but I have to run manually the php server, every time, giving the command in a terminal window via ssh.

How can I start the php server at boot of my OMV machine, and run it in background, continuously & all the time?

I'm inexperienced in scripting and similar things, so I would like to ask for help...

Thank you very much!
Federico

gderf · 4. August 2017

Add that command to the file /etc/rc.local above the line that says exit 0

macom · 4. August 2017

You can run the command as "scheduled job" at reboot.
In the left collumn of OMV GUI you will find the section "scheduled job".

donh · 4. August 2017

It would be better to write an init script. An init script can restart your program if it dies, the others only happen when you reboot.

A quick google (Calibre OPDS server init script) found this. https://gist.github.com/razrichter/4157867 Have not looked too close at it so use at your own risk.

drinks2go · 4. August 2017

Rc.local is deprecated in debian 9 no? Better to fool around with an init script.

gderf · 4. August 2017

Zitat von drinks2go

Rc.local is deprecated in debian 9 no? Better to fool around with an init script.

Not according to this:

https://stackoverflow.com/ques…n-debian-9-debian-stretch

drinks2go · 4. August 2017

From your link:

"rc.local is being deprecated"

Best not to rely on it then. In this case it's a bit of a kludge

gderf · 4. August 2017

Zitat von drinks2go

From your link:

"rc.local is being deprecated"

Best not to rely on it then. In this case it's a bit of a kludge

But your position is not applicable until OMV is on Stretch. And right now, it isn't.

drinks2go · 4. August 2017

That's fair, but it's not the "proper" use per se of rc local.

Because it's basically an application, it would be better to write a systemd init script for such uses.

If he only starts the app on each multiuser runlevel (ie. rc local), if it failed for some reason he'd have to ssh into the box to restart it. For this reason alone it makes much more sense to write an init script.

It's not terribly difficult to write a simple init script-- the one linked in this thread however will probably not work without modification as it's looks like it is for calibre itself and not the homebrew app the original poster is using- though I could be mistaken.

ryecoaaron · 5. August 2017

Actually, on OMV 3.x, you should write a systemd unit file. Would be very simple:

Code

[Unit]
Description=start php app
DefaultDependencies=no
After=network.target


[Service]
Type=oneshot
ExecStart=/usr/bin/php -S 192.168.1.96:8080


[Install]
WantedBy=multi-user.target

Alles anzeigen

Create that file at /lib/systemd/system/php-app.service and enable it with systemctl enable php-app.service

dr_nero · 7. August 2017

Thank you all!

@ryecoaaron: I've created/lib/systemd/system/COPS.service

However, my machine runs OMV 2: perhaps that's why
systemctl enable COPS.service
returns
-bash: systemctl: command not found

I can put your script in /etc/init.d/ folder, and then automate it with update-rc.d?

I've read something similar in Debian documentation...

In the meantime, I try the solution proposed by @macom

ryecoaaron · 7. August 2017

Zitat von dr_nero

I can put your script in /etc/init.d/ folder, and then automate it with update-rc.d?

Nope. That is a unit file that only works with systemd. An init script for sysvinit that OMV 2.x uses is a bit more complicated.

Jetzt mitmachen!