[systemd-devel] masked services and a lot of warnings

David Strauss david at davidstrauss.net
Sun Feb 17 17:17:49 PST 2013


Couldn't you also just disable or mask the sources of activation?

On Sun, Feb 17, 2013 at 11:12 AM, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>
> Am 17.02.2013 19:48, schrieb Cristian Rodríguez:
>> El 17/02/13 15:37, Reindl Harald escribió:
>>>
>>>
>>> Am 17.02.2013 19:33, schrieb Cristian Rodríguez:
>>>> El 17/02/13 14:33, Reindl Harald escribió:
>>>>> can we gat rid of this messages somehow?
>>>>> i know that they are masked and can not be started
>>>>> this as the reason to mask them
>>>>>
>>>>> nobody needs upower on a virtual machine because
>>>>> he connects via SSH and opens a X application with
>>>>> X-Forwarding
>>>>
>>>> Huh ? isnt that bug in the unit instead..
>>>
>>> in which one?
>>>
>>> this happens as example starting kate (a kde text editor)
>>>
>>>> there is no need to mask it , just set ConditionVirtualization=false
>>>
>>> again: where?
>>
>> vim /etc/systemd/system/upower.service
>>
>> .include /usr/lib/systemd/system/upower.service
>>
>> [Unit]
>> ConditionVirtualization=false
>>
>>
>> systemctl --system daemon-reload
>
> does not work inside a vmware guest
> yes, systemctl daemon-reload was executed
>
> and so again: why the hell are the warnings about masked services
> yes they are masked for a reason
>
> the same on yum updates if you masked atd.service and
> google-crhome try to restart it - i know that it is masked
> ___________________________________
>
> Feb 17 20:09:18 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
> name='org.freedesktop.UPower' unit='upower.service'
> Feb 17 20:09:18 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
> unit='upower.service'
> Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
> 'org.freedesktop.UPower': timed out
> Feb 17 20:09:43 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
> Feb 17 20:09:43 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
> unit='upower.service'
> Feb 17 20:09:43 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
> name='org.freedesktop.UPower' unit='upower.service'
> Feb 17 20:10:08 buildserver dbus-daemon[450]: dbus[450]: [system] Failed to activate service
> 'org.freedesktop.UPower': timed out
> Feb 17 20:10:08 buildserver dbus[450]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
> Feb 17 20:10:11 buildserver dbus-daemon[450]: dbus[450]: [system] Activating via systemd: service
> name='org.freedesktop.UPower' unit='upower.service'
> Feb 17 20:10:11 buildserver dbus[450]: [system] Activating via systemd: service name='org.freedesktop.UPower'
> unit='upower.service'
>
> [root at buildserver:~]$ cat /etc/systemd/system
> system/                system.conf            systemd-journald.conf  systemd-logind.conf
> [root at buildserver:~]$ cat /etc/systemd/system/upower.service
> .include /usr/lib/systemd/system/upower.service
>
> [Unit]
> ConditionVirtualization=false
>
>
>
>
>
>
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>



--
David Strauss
   | david at davidstrauss.net
   | +1 512 577 5827 [mobile]


More information about the systemd-devel mailing list