Under the old C6 I put an entry in rc.local to run my programs I want. We will call it /path/boot.sh Worked fine.
Under C7 I have created a new service file for systemd. It looks like:
Try this https://ask.fedoraproject.org/en/question/26898/what-is-the-auto-start-file-like-rclocal/
18.7.2016 6.42 ip. “Jerry Geis” kirjoitti:
There’s nothing that jumps out at me as incorrect, if what you say is true, that it’s hung. You might be better off with a oneshot job instead of forking.
Also, the benefit of running this in CentOS7 with systemd is that you can examine the journal to see what exactly its been doing, so if your script is verbose, you should be able to see what its doing. Just run
‘journalctl -xl -u YOURUNITNAME.service’. Anything sent to stdout, stderr, syslog or the journal should be there. Perhaps that’ll help?
I manage some packages that use dkms for building kernel modules for each new kernel, perhaps that might be a nice structure for you to use to build your kmods? The ‘dkms’ package is part of EPEL and its home page is here: http://linux.dell.com/dkms
Note: the accepted answer there is wrong, it should be
/etc/rc.d/rc.local, not /etc/rc.local. Anyway, using
/etc/rc.d/rc.local won’t be much different from what the current service is doing.
I think it’s related to either
You might want to check out these options for your service definition.