On Sun, Nov 22, 2015 at 4:04 PM, Lennart Poettering
wrote:
> On Sun, 22.11.15 15:26, Francis Moreau (francis.m...@gmail.com) wrote:
>
>> Hi,
>>
>> While rebooting, It seems to me that shutting down services while
>> unmounting some FS at the same time in an unordered
what is the relationship between systemd-logind and polkit.Because when I do
like this "systemd-analyze plot ",it tells me that "failed to list
units:Access denied".About this ,I have no idea.
yan...@iscas.ac.cn
___
systemd-devel mailing list
On Mon, Nov 23, 2015 at 11:00 AM, yan...@iscas.ac.cn wrote:
>
> what is the relationship between systemd-logind and polkit.Because when I do
> like this "systemd-analyze plot ",it tells me that "failed to list
> units:Access denied".About this ,I have no idea.
It's not
I remember Debian had an oddly restrictive policy for systemd bus access
(though it seems to be fixed now?).
On Mon, Nov 23, 2015, 14:24 Andrei Borzenkov wrote:
> On Mon, Nov 23, 2015 at 11:00 AM, yan...@iscas.ac.cn
> wrote:
> >
> > what is the
Colin Guthrie wrote
> Zbigniew Jędrzejewski-Szmek wrote on 11/11/15 15:55:
>> On Wed, Nov 11, 2015 at 04:39:23PM +0100, Frank Steiner wrote:
>>> Isn't there an easy way to figure out if this script is running
>>> inside the boot process? Some variable set or not yet set?
>> You can use systemctl
Hi,
on one of my serves I have a LVM that, due to an error in my lvm.conf,
couldn't be mounted on boot. But I didn't get a maintenance shell as
I usually got on other servers, the output just stopped after complaining
with
[ TIME ] Timed out waiting for device
2015-11-23 13:32 GMT+01:00 Mantas Mikulėnas :
> I remember Debian had an oddly restrictive policy for systemd bus access
> (though it seems to be fixed now?).
The Debian systemd package never diverged from the upstream D-Bus policy afair.
*But* in the past, the systemd-shim
23.11.2015 23:59, Steve Abner пишет:
During shut down I get:
systemd[1]: Requested transaction contradicts existing jobs:
Transaction is destructive.
systemd-networkd.socket: Failed to queue service startup job (Maybe
the service file is missing or not a non-template unit?): Transaction is
24.11.2015 06:37, Jesse Cobra пишет:
It is not happening at this moment but last week I saw these messages in
dmesg:
[ 755.629529] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit dmesg.service is masked.
[ 5177.325999] systemd[1]: Cannot add dependency job for
Hi Andrei Borzenkov:
I do it as sam , the administrator,not root.And when I do it as root,it
works.
as you say,at the /run/user/1000/, there is no "dbus-session"
yan...@iscas.ac.cn
From: Andrei Borzenkov
Date: 2015-11-23 20:24
To: yan...@iscas.ac.cn
CC: systemd-devel
Subject: Re:
I wish I had more info.
Does systemd itself have a log file?
Not the service I am creating but systemd itself.
--
Message: 5
Date: Sat, 21 Nov 2015 11:58:51 +0100
From: Reindl Harald
To: systemd-devel@lists.freedesktop.org
Subject: Re:
Year, you are right.Acturally,what I use is Debian package.And at the
/run/user/1000/, there is no "dbus-session"
yan...@iscas.ac.cn
From: Mantas Mikulėnas
Date: 2015-11-23 20:32
To: Andrei Borzenkov; yan...@iscas.ac.cn
CC: systemd-devel
Subject: Re: [systemd-devel] about administator
Am 24.11.2015 um 01:49 schrieb Jesse Cobra:
I wish I had more info.
jesus christ you talk about "I often seesystemd events logged in dmesg"
without posting them
Does systemd itself have a log file?
Not the service I am creating but systemd itself.
--
It is not happening at this moment but last week I saw these messages in
dmesg:
[ 755.629529] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit dmesg.service is masked.
[ 5177.325999] systemd[1]: Cannot add dependency job for unit
dmesg.service, ignoring: Unit
I have a case where I get a report of:
systemd-networkd[260]: wlan0 : found matching network
'/etc/systemd/network/11-dhcp-wlan0.network', based on potentially
unpredictable ifname
From what I gathered of unique ids wlan0 shouldn't exist. I see where:
forcedeth :00:0a.0
On Mon, 2015-11-23 at 15:09 +0100, Michael Biebl wrote:
> 2015-11-23 13:32 GMT+01:00 Mantas Mikulėnas :
> > I remember Debian had an oddly restrictive policy for systemd bus
> > access
> > (though it seems to be fixed now?).
>
> The Debian systemd package never diverged from
16 matches
Mail list logo