Hey,
bus_event_loop_with_idle seems very useful function in terms of
shutting down services race free and it is both for kdbus/dbus-daemon.
Any plans making it public?
Umut
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists
On Thu, Nov 19, 2015 at 01:57:22PM +0800, yan...@iscas.ac.cn wrote:
> In my machine,therr is nohing in /run/user/,so there is problem with
> pam_systemd or the systemd-logind and do you think where is it?
Hi,
This sort of integration should be made by distribution. Please contact
develop
In my machine,therr is nohing in /run/user/,so there is problem with
pam_systemd or the systemd-logind and do you think where is it?
yan...@iscas.ac.cn
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/m
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Nov 18, 2015 at 01:06:02AM +0100, Marek wrote:
> Why shouldn't they matter? Can you clarify?
Why would they matter? Are you having problems that things are not
working properly for you?
> Whe
Am 18.11.2015 um 16:00 schrieb hans vasquez morales:
When I log in to my pc, the following message is
Welcome emergency mode! to view system logs "journalctl -xb"
after inserting the command:
localhost system-fsck[503]: fsck failed with error 8
run fsck *manually* in the emergency shell sin
When I log in to my pc, the following message is
Welcome emergency mode! to view system logs "journalctl -xb"
after inserting the command:
localhost system-fsck[503]: fsck failed with error 8
localhost rpcbind[312]: rpcbind terminating on signal "rpcbind -w"
localhost system[1]: /usr/lib/syst
On 18 November 2015 at 13:23, Lennart Poettering wrote:
> The problem is with actually invoking processes such as the fuse.sshfs
> one as a non-root user.
But in my case there are no non-root processes! uid/gid options is
used just for *ownership of files and directories* under the mount
point, t
On Wed, 18.11.15 13:02, Igor Bukanov (i...@mir2.org) wrote:
> On 18 November 2015 at 12:28, Lennart Poettering
> wrote:
> > We don't support that. Invoking user processes from a system context
> > is something we generally avoid.
>
> Could you clarify how this is related to an ability to invoke
On 18 November 2015 at 12:28, Lennart Poettering wrote:
> We don't support that. Invoking user processes from a system context
> is something we generally avoid.
Could you clarify how this is related to an ability to invoke a user
process? For example, I can explicitly pass uid=1000,gid=1000 as a
On Wed, 18.11.15 11:58, Igor Bukanov (i...@mir2.org) wrote:
> Hello,
>
> I am trying to translate an autofs map into systemd unit files, but I
> could not see how to pass to the mount command an option refering to
> the user who accessed the mount dir. For example, the automap
> contains:
>
> /m
Hello,
I am trying to translate an autofs map into systemd unit files, but I
could not see how to pass to the mount command an option refering to
the user who accessed the mount dir. For example, the automap
contains:
/mount/dir -fstype=fuse.sshfs,...,id=$UID,gid=$GID remote_user@host:/dir
which
Jay Burger writes:
> Hi,
>
> I am a complete newbie to this list and I am trying to find
> out if I can patch my systemd-211 to include the FailureAction
> feature. If so where can I obtain the patche(s)?
>
> We are using the yocto daisy distribution which has systemd-211
> and due to silly proc
Hey!
We just tagged a new release, slightly delayed due to the conference.
It includes several new features, some old cruft removed, and many
bugfixes!
CHANGES WITH 228:
* A number of properties previously only settable in unit
files are now also available as properties to set
On Wed, 18 Nov 2015, yan...@iscas.ac.cn wrote:
yeah, I compare it to ubuntu.It also can not work.
Hello,
I suggest that this is probably something you need to bring up on Ubuntu's
bug tracker rather than here on the systemd mailing list. If you have
pam_systemd installed (via the libpam-sys
yeah, I compare it to ubuntu.It also can not work.
yan...@iscas.ac.cn
From: Mantas Mikulėnas
Date: 2015-11-18 16:37
To: yan...@iscas.ac.cn
CC: systemd-devel
Subject: Re: Re: [systemd-devel] about systemd-logind
On Wed, Nov 18, 2015 at 10:34 AM, yan...@iscas.ac.cn wrote:
About PAM,I am not c
On Wed, Nov 18, 2015 at 10:34 AM, yan...@iscas.ac.cn
wrote:
> About PAM,I am not clear.In my computer,there is pam_systemd.so in
> /lib/x86_64-linux-gnu/security/
> . And it does not matter.
>
Like I said, it needs to be listed in your PAM configuration – usually
/etc/pam.d/system-login o
About PAM,I am not clear.In my computer,there is pam_systemd.so in
/lib/x86_64-linux-gnu/security/ . And it does not matter.
yan...@iscas.ac.cn
From: Mantas Mikulėnas
Date: 2015-11-18 16:28
To: yan...@iscas.ac.cn
CC: systemd-devel
Subject: Re: Re: [systemd-devel] about systemd-logind
On
On Wed, Nov 18, 2015 at 10:23 AM, yan...@iscas.ac.cn
wrote:
> Do you mean /lib/x86_64-linux-gnu/security/pam_systemd.so? thank you!
>
Linux PAM configurations normally don't require the full path, but yes.
--
Mantas Mikulėnas
___
systemd-devel maili
Do you mean /lib/x86_64-linux-gnu/security/pam_systemd.so? thank you!
yan...@iscas.ac.cn
From: Mantas Mikulėnas
Date: 2015-11-18 15:59
To: yan...@iscas.ac.cn
CC: systemd-devel
Subject: Re: [systemd-devel] about systemd-logind
On Wed, Nov 18, 2015 at 9:07 AM, yan...@iscas.ac.cn wrote:
Hi,when
19 matches
Mail list logo