Description of problem: https://fedoraproject.org/wiki/Features/SysVtoSystemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 512249 [details] Native systemd service file apmd What's the current status on this? I've submitted totally untested service file based on the init script and note that faik modules should be loaded via autoloading based on bus information, or via /etc/modules-load.d/*.conf. and unloading a module from the kernel should not be done except for debugging purposes. Thus you should propably rop a conf file into /etc/modules-load.d for the module If you dont have the time to package this make note of that on this bug and I can see if I can find a proven packager you can package this for you... https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd https://fedoraproject.org/wiki/Packaging:Tmpfiles.d
Ping you component is part of the Base group hence we need to get some move on this..
Hi, APM is quite historical. So I was checking for a support of this service firstly. Well, I'm searching for hw to test otherwise I'd use your attached unit file. But as you mentioned loading kernel module should be separated into /etc/module-load.d/. This would be only change against attached file. Any comments?
Nope not really you would just create a file called apm.conf containing something like.. # Load apm.ko at boot apm And remove the line ExecStartPre=-/sbin/modprobe -qab apm