On 2024-07-21 19:20, Dave Howorth wrote:
On Sun, 21 Jul 2024 20:42:45 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:
The correct procedure is as follows;
1. $ systemctl enable freshclam.timer
2. $ systemctl start freshclam.timer
3. $ systemctl start freshclam.service
4. $ systemctl enable clamd.service
5. $ sudo clamd
If you need sudo to run clamd, don't you also need sudo to run systemctl (except for systemctl status ) ?
Right. Also, if the timer is enabled and running, the service doesn't need to be active — at least that's my understanding, by looking at logrotate.timer and logrotate.service in leap. In this case, freshclam in Leap doesn't have a timer, so the instructions in the wiki are appropriate for Leap. TW is subject to quick changes, so somebody apparently decided to use a timer instead. Telcontar:~ # systemctl status freshclam.timer Unit freshclam.timer could not be found. Telcontar:~ # Somebody changed the instructions, and now talks of a timer, which is incorrect for Leap 15.5 at least. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)