On 2016-05-20 08:17, Per Jessen wrote:
> Carlos E. R. wrote:
>
>> On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote:
>>> Per Jessen wrote:
>>>
I though I would be able to reduce this by adding "Loglevel=notify"
to /etc/systemd/user.conf, but:
systemd[2034]:
Carlos E. R. wrote:
> On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote:
>> 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':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote:
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
On 2016-05-19 23:02, Carlos E. R. wrote:
>
>> This other message remains, every five minutes, sometimes twice:
>
>> <3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job
>> for unit udev.service, ignoring: Unit udev.service failed to load: No such
>> file or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, 2016-05-19 at 17:06 +0200, Carlos E. R. wrote:
This other message remains, every five minutes, sometimes twice:
<3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job
for unit udev.service, ignoring: Unit
Carlos E. R. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote:
>> Per Jessen wrote:
>>
>>> I though I would be able to reduce this by adding "Loglevel=notify"
>>> to /etc/systemd/user.conf, but:
>>>
>>> systemd[2034]:
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