ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014351ClearOSapp-suvapublic2017-04-11 09:162021-11-09 05:56
Reporterdloper 
Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionunable to reproduce 
PlatformOSOS Version
Product Version7.3.1 
Target VersionFixed in Version 
Summary0014351: suvad service unlinked
DescriptionNot 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
Additional InformationThe 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
TagsNo tags attached.
Attached Files

- Relationships

-  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.

- Issue History
Date Modified Username Field Change
2017-04-11 09:16 dloper New Issue
2017-04-11 09:26 user2 Note Added: 0005331
2017-04-11 09:26 user2 Status new => confirmed
2017-04-18 10:56 user2 Target Version 7.3.1 Updates =>
2021-11-09 05:56 NickH Status confirmed => closed
2021-11-09 05:56 NickH Resolution open => unable to reproduce