Tumbleweed - error enabling freshclam?
All, I went to start freshclam.service as stated in https://en.opensuse.org/ClamAV and I received the following error: # 02:01 wizard:.../cnf/gtk4/themes] # sc enable freshclam The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl. Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. freshclam.timer did enable properly. Do we not need to enable freshclam anymore? If so, is the wiki out of date? -- David C. Rankin, J.D.,P.E.
Op zaterdag 20 juli 2024 09:03:56 CEST schreef David C. Rankin:
All,
I went to start freshclam.service as stated in https://en.opensuse.org/ClamAV and I received the following error:
# 02:01 wizard:.../cnf/gtk4/themes] # sc enable freshclam The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=, Also=, or Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified.
freshclam.timer did enable properly. Do we not need to enable freshclam anymore? If so, is the wiki out of date?
The website says: sudo systemctl start freshclam sudo systemctl enable freshclam.timer As you stated above you did "sc enable freshclam", which is not what the ^^^^^^ website says. -- fr.gr. member openSUSE Freek de Kruijf
On 7/20/24 3:09 AM, Freek de Kruijf wrote:
The website says: sudo systemctl start freshclam sudo systemctl enable freshclam.timer
As you stated above you did "sc enable freshclam", which is not what the ^^^^^^ website says.
Thank you, I guess I'm just old school. You want a service started it's systemctl start unitfile If you want it started on boot, it's systemctl enable unitfile I guess freedesktop is now changing that as well. In 15.4 you had to "enable" freshclam, e.g. $ l /mnt/wz/etc/systemd/system/multi-user.target.wants/ <snip> freshclam.service -> /usr/lib/systemd/system/freshclam.service -- David C. Rankin, J.D.,P.E.
Op zaterdag 20 juli 2024 10:23:25 CEST schreef David C. Rankin:
On 7/20/24 3:09 AM, Freek de Kruijf wrote:
The website says: sudo systemctl start freshclam sudo systemctl enable freshclam.timer
As you stated above you did "sc enable freshclam", which is not what the
^^^^^^
website says.
Thank you,
I guess I'm just old school. You want a service started it's
systemctl start unitfile
If you want it started on boot, it's
systemctl enable unitfile
I guess freedesktop is now changing that as well. In 15.4 you had to "enable" freshclam, e.g.
$ l /mnt/wz/etc/systemd/system/multi-user.target.wants/ <snip> freshclam.service -> /usr/lib/systemd/system/freshclam.service
Now the timer does the starting regularly. So freshclam does not need to stay active in the system anymore. -- fr.gr. member openSUSE Freek de Kruijf
Hello, In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <2704039.vuYhMxLoTh@eiktum> Date & Time: Sat, 20 Jul 2024 10:09:58 +0200 [FdeK] == Freek de Kruijf <freek@opensuse.org> has written: FdeK> Op zaterdag 20 juli 2024 09:03:56 CEST schreef David C. Rankin: [...] FdeK> The website says: FdeK> sudo systemctl start freshclam FdeK> sudo systemctl enable freshclam.timer FdeK> As you stated above you did "sc enable freshclam", which is not FdeK> what the ^^^^^^ FdeK> website says. If freshclam.timer is not started before start freshcalm.service , an error like David's will occur and clamav will not run. The correct procedure for starting clamav is as follows; 1. $ systemctl enable freshclam.timer 2. $ systemctl start freshclam.timer 3. $ systemctl start freshclam.service 4. clamd Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
Hello, Sorry for mistake. In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <87zfqc2z3v.wl-nomiya@lake.dti.ne.jp> Date & Time: Sat, 20 Jul 2024 18:26:28 +0900 [MN] == Masaru Nomiya <nomiya@lake.dti.ne.jp> has written: [...] MN> The correct procedure for starting clamav is as follows; MN> 1. $ systemctl enable freshclam.timer MN> 2. $ systemctl start freshclam.timer MN> 3. $ systemctl start freshclam.service MN> 4. clamd 4. $ sudo clamd Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
Hello, So sorry. In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <87y15w2xel.wl-nomiya@lake.dti.ne.jp> Date & Time: Sat, 20 Jul 2024 19:03:14 +0900 [MN] == Masaru Nomiya <nomiya@lake.dti.ne.jp> has written: [...] MN> The correct procedure for starting clamav is as follows; MN> 1. $ systemctl enable freshclam.timer MN> 2. $ systemctl start freshclam.timer MN> 3. $ systemctl start freshclam.service MN> 4. clamd MN> 4. $ sudo clamd 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 It is too hot every day .....! Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ Think. -- The IBM slogan --
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 ) ?
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)
Hello, In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <20240721182038.6e8c7bd0@acer-suse.fritz.box> Date & Time: Sun, 21 Jul 2024 18:20:38 +0100 [DH] == Dave Howorth <dave@howorth.org.uk> has written: DH> On Sun, 21 Jul 2024 20:42:45 +0900 DH> Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote: MN> > The correct procedure is as follows; MN> > 1. $ systemctl enable freshclam.timer MN> > 2. $ systemctl start freshclam.timer MN> > 3. $ systemctl start freshclam.service MN> > 4. $ systemctl enable clamd.service MN> > 5. $ sudo clamd DH> If you need sudo to run clamd, don't you also need sudo to run DH> systemctl (except for systemctl status ) ? My Bad! In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <049bc92b-c4d0-4f92-9d46-2e6a127e6a6e@telefonica.net> Date & Time: Sun, 21 Jul 2024 19:50:52 +0200 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: [...] CER> In this case, freshclam in Leap doesn't have a timer, so the CER> instructions in the wiki are appropriate for Leap. TW is subject CER> to quick changes, so somebody apparently decided to use a timer CER> instead. CER> Telcontar:~ # systemctl status freshclam.timer CER> Unit freshclam.timer could not be found. CER> Telcontar:~ # CER> Somebody changed the instructions, and now talks of a timer, CER> which is incorrect for Leap 15.5 at least. [...] I don't know what you are talking about, but leap15.6 has a freshclam.timer. To be precise, freshclam.timer was added as a customization by openSUSE after clamav 1.0.0, and is not present in upstream. I guess leap 15.5 was provided with pre-1.0.0 clamav. Needless to say, David is talking about Tumbleweed. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
On 2024-07-22 02:37, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <20240721182038.6e8c7bd0@acer-suse.fritz.box> Date & Time: Sun, 21 Jul 2024 18:20:38 +0100
[DH] == Dave Howorth <dave@howorth.org.uk> has written:
DH> On Sun, 21 Jul 2024 20:42:45 +0900 DH> Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:
MN> > The correct procedure is as follows;
MN> > 1. $ systemctl enable freshclam.timer
MN> > 2. $ systemctl start freshclam.timer
MN> > 3. $ systemctl start freshclam.service
MN> > 4. $ systemctl enable clamd.service
MN> > 5. $ sudo clamd
DH> If you need sudo to run clamd, don't you also need sudo to run DH> systemctl (except for systemctl status ) ?
My Bad!
In the Message;
Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <049bc92b-c4d0-4f92-9d46-2e6a127e6a6e@telefonica.net> Date & Time: Sun, 21 Jul 2024 19:50:52 +0200
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
[...] CER> In this case, freshclam in Leap doesn't have a timer, so the CER> instructions in the wiki are appropriate for Leap. TW is subject CER> to quick changes, so somebody apparently decided to use a timer CER> instead.
CER> Telcontar:~ # systemctl status freshclam.timer CER> Unit freshclam.timer could not be found. CER> Telcontar:~ #
CER> Somebody changed the instructions, and now talks of a timer, CER> which is incorrect for Leap 15.5 at least. [...]
I don't know what you are talking about, but leap15.6 has a freshclam.timer.
Leap 15.5 doesn't. Telcontar:~ # locate freshclam.timer Telcontar:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.5" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.5" PRETTY_NAME="openSUSE Leap 15.5"
To be precise, freshclam.timer was added as a customization by openSUSE after clamav 1.0.0, and is not present in upstream.
I guess leap 15.5 was provided with pre-1.0.0 clamav.
Telcontar:~ # rpm -q clamav clamav-0.103.11-150000.3.50.1.x86_64 Telcontar:~ #
Needless to say, David is talking about Tumbleweed.
Yes. But the instructions on the wiki were for the previous version. This change also means that the settings in: /etc/freshclam.conf may not apply. Specifically I am thinking of: # Number of database checks per day. # Default: 12 (every two hours) Checks 4 I don't see advantage of changing upstream defaults. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, Sorry for late reply. In the Message; Subject : Re: Tumbleweed - error enabling freshclam? Message-ID : <c7ccf1b0-ee16-4fed-8699-710de84463f1@telefonica.net> Date & Time: Mon, 22 Jul 2024 11:51:48 +0200 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: [...] CER> I don't see advantage of changing upstream defaults. Hmmm, it sure is.... Upstream has clamav-freshclam.service, clamav-freshclam-once.service, and clamav-freshclam-once.time, but these are for clamav-milter. freshclam.service and freshclam.timer automate virus database updates, but make clamav harder to use...... Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
participants (5)
-
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Freek de Kruijf -
Masaru Nomiya