ClearFoundation Tracker - ClearOS
View Issue Details
0014351ClearOSapp-suvapublic2017-04-11 09:162021-11-09 05:56
dloper 
 
normalminorsometimes
closedunable to reproduce 
7.3.1 
 
0014351: suvad service unlinked
Not sure what causes it or if it has always been an issue but the symbolic link for /etc/systemd/system/suva.service is broken because it is improperly named.

Should be suvad.service -> /usr/lib/systemd/system/suvad.service which may already exist
The following cleans up the condition:

if [ -L /etc/systemd/system/multi-user.target.wants/suva.service ]; then if [ -f /usr/lib/systemd/system/suvad.service ]; then rm -f /etc/systemd/system/multi-user.target.wants/suva.service; if [ -L /etc/systemd/system/multi-user.target.wants/suvad.service ]; then :; else ln -s /usr/lib/systemd/system/suvad.service /etc/systemd/system/multi-user.target.wants/suvad.service; systemctl start suvad; fi; else exit 1; fi; fi
No tags attached.
Issue History
2017-04-11 09:16dloperNew Issue
2017-04-11 09:26user2Note Added: 0005331
2017-04-11 09:26user2Statusnew => confirmed
2017-04-18 10:56user2Target Version7.3.1 Updates =>
2021-11-09 05:56NickHStatusconfirmed => closed
2021-11-09 05:56NickHResolutionopen => unable to reproduce

Notes
(0005331)
user2   
2017-04-11 09:26   
That is a leftover from the transition from "suva/SysV" to "suvad/systemd". Systemd ignores it, so I would consider this a very low priority.