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]: [/etc/system
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': Ope
-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 level'notify'
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 directory.
-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 udev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, 2016-05-19 at 09:17 +0200, Per Jessen wrote:
Carlos E. R. wrote:
Loglevel=notice does the trick.
Not here.
I get:
# <3.4> 2016-05-19 06:10:01 Telcontar systemd 12279 - -
# [/etc/systemd/user.conf:12] Unknown lvalue 'Loglevel
H
Thanks Per for the LogLevel hint!
Just tested, works. Instead of modifying /etc/systemd/user.conf I opted for
creating a user@.service dropin that overrides ExecStart, like this:
HOST:~ # cat /etc/systemd/system/user@.service.d/notice.conf
[Service]
ExecStart=
ExecStart=-/usr/lib/systemd/system
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]: [/e
-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 level'notify'
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)
http:/
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 it
Patrick Schaaf wrote:
> And another one with latest systemd on 13.1:
>
> triggered by cronjobs running as some normal user, my logs now
> "constantly" contain the list of messages shown below.
>
> That was not the case with earlier systemd packages, even earlier 210
> ones.
>
> I already have s
And another one with latest systemd on 13.1:
triggered by cronjobs running as some normal user, my logs now
"constantly" contain the list of messages shown below.
That was not the case with earlier systemd packages, even earlier 210 ones.
I already have some other rsyslog filters for similar stu
13 matches
Mail list logo
