thats what i assumed/knew just checking. It may be something odd with this particular lxc container, but it works well with the others, so the (self start) hack allows me to deploy and test code properly.
I'll dig around or perhaps just try a complete purge of all things clam and reinstall. On Mon, Aug 29, 2016 at 9:51 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 29.08.2016 um 15:34 schrieb Jeff Dyke: > >> our config locations for the .service files are in slightly different >> areas, so do you mind saying what distro you're running >> > > Fedora but it does not matter > > the whole concept of systemd is when you disable a existing service and > place a unit with the same name below /etc/systemd/system/ that "systemctl > enable name.service" enables this one and the distro shipped is no longer > used in any way > > the same for .timer. .socket and what not else > > /etc/systemd/system/ has the same strcuture as /usr/lib/systemd/system/ > and is meant for local overrides / replacements > > > _______________________________________________ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
