Per Jessen wrote:
> I though I would be able to reduce this by adding "Loglevel=notify"
> to /etc/systemd/user.conf, but:
>
> systemd[2034]: [/etc/systemd/user.conf:11] Invalid log level'notify':
> Operation not permitted
Loglevel=notice does the trick.
--
Per Jessen, Zürich (18.7°C)
On 2016-05-18 08:38, Per Jessen wrote:
> Patrick Schaaf wrote:
>> I already have some other rsyslog filters for similar stuff, but the
>> amount of different messages here, makes me reluctant to go down the
>> fiter-it-away route further...
>>
>> Maybe somebody knows the root cause + could make
Patrick Schaaf wrote:
> With the latest systemd etc. updates for 13.1 on my production
> webservers, I started to get these messages, several times a day:
>
> 2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service:
> Got notification message from PID 14342, but reception only
