The problem is I asked a question, and I expected an answer. I see two possible options:
1. Forking clamd is not good. Foreground as a command line and config file option will be removed. 2. Forking clamd is ok, or no problem. The choice is to the user through the command line or config file. The --foreground=true= in the systemd service will be removed. Doing nothing here seems bad coding to me. But I'm not a developer, so I just asked. Met vriendelijke groet, Paul Guijt -----Oorspronkelijk bericht----- Van: Sebastian Andrzej Siewior <[email protected]> Verzonden: vrijdag 13 april 2018 21:42 Aan: Paul Guijt <[email protected]> CC: [email protected] Onderwerp: Re: [Pkg-clamav-devel] --foreground in /lib/systemd/service/clamav-daemon.service deliberately? On 2018-04-12 22:38:15 [+0200], Paul Guijt wrote: > Hi team, > > Not knowing whether it's a bug or a feature, I thought I'd ask you first. > > I have Raspbian stretch with clamav-daemon 0.99.4+dfsg-1+deb9u1 running. > > In htop I saw /usr/sbin/clamd --foreground=true, although the > /etc/clamav/clamav.conf states: > # Don't fork into background. > # Default: no > #Foreground yes > > Digging into it I noticed in /lib/systemd/system/clamav-daemon.service: > [Service] > ExecStart=/usr/sbin/clamd --foreground=true > > Is that deliberate, perhaps even documented somewhere? > > I've been told that forking is a good thing, not only at dinner. So what is the problem or what do you expect to happen? > Regards, > Paul Guijt Sebastian _______________________________________________ Pkg-clamav-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clamav-devel
