- Edited
Hi everyone, recently, I changed some hardware in my computer, and unfortunately, lost my init files for 66. Over the last few days, I've been remaking them, however, one service has been giving me quite a bit of trouble. A fancontrol script for AMDGPU written in bash. I tried simply translating the systemd service into 66 syntax, which left me with:
[main]
@ type = oneshot
@ version = 0.1.0
@ description = "AMDGPU fancontrol for 66"
@ user = ( root )
@ options = ( log )
[start]
@ build = auto
@ execute = ( execl-cmdline -s { /usr/bin/amdgpu-fancontrol } )
however, when I try enable this service and reboot, my computer hangs at all-runtime. When trying to start the service with 66-start -v4, it hangs after giving me the following:
66-start(src/lib66/ssexec_start.c: ssexec_start(): 367): tracing: sanitize atomic services list...
66-start(src/lib66/ssexec_start.c: ssexec_start(): 372): tracing: start atomic services list ...
s6-rc: info: bringing selected services up
s6-rc: info: service s6rc-oneshot-runner: already up
s6-rc: info: service amdgpu-fancontrol: starting
s6-ipcclient: connected to /run/66/tree/0/root/servicedirs/s6rc-oneshot-runner/s
One thing I did notice, is that using 66-start actually does start the fans, but not the service.