Am 05.12.2017 um 19:52 schrieb Reindl Harald:
Am 05.12.2017 um 19:34 schrieb Colony.three:
Am 05.12.2017 um 08:13 schrieb Colony.three:
As Red Hat hasn't solved the problem of unix:sockets, I had to make
my own systemd files. But there's a little problem.
clamd.socket
[Unit]
Description=S
Am 05.12.2017 um 19:34 schrieb Colony.three:
Am 05.12.2017 um 08:13 schrieb Colony.three:
As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
systemd files. But there's a little problem.
clamd.socket
[Unit]
Description=Socket for Clam AntiVirus userspace daemon
Docum
> Am 05.12.2017 um 08:13 schrieb Colony.three:
>
>> As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
>> systemd files. But there's a little problem.
>>
>> clamd.socket
>>
>> [Unit]
>> Description=Socket for Clam AntiVirus userspace daemon
>> Documentation=man:clamd(8) man
Am 05.12.2017 um 08:13 schrieb Colony.three:
As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
systemd files. But there's a little problem.
clamd.socket
==
[Unit]
Description=Socket for Clam AntiVirus userspace
As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
systemd files. But there's a little problem.
clamd.socket
==
[Unit]
Description=Socket for Clam AntiVirus userspace daemon
Documentation=man:clamd(8) man:clamd.conf(