23.01.2016 01:19, Armin K. пишет:
>
> Now, to the original question: Once PAM closes the session (once logout is
> received),
> should systemd --user daemon terminate as well? Currently, that's not the
> case on my
> system.
>
As far as I understand systemd --user instance is supposed to be
pe
22.01.2016 20:23, Mantas Mikulėnas пишет:
>>
>
> systemd-ask-password(1) mentions being able to cache passwords in a kernel
> keyring, but I'm not sure if systemd-cryptsetup actually makes use of that.
>
Current GIT should be doing it automatically. This is commit e287086b
which is released sinc
On 23.01.2016 00:37, Kai Krakow wrote:
> Am Sat, 23 Jan 2016 00:20:34 +0100
> schrieb "Armin K." :
>
>>> My first guess is: Does your Xsession try to spawn dbus itself?
>>> Have you tried commenting it out? Should be in /etc/X11 or
>>> somewhere in the session files installed by lightdm.
>>>
>>
Am Sat, 23 Jan 2016 00:20:34 +0100
schrieb "Armin K." :
> > My first guess is: Does your Xsession try to spawn dbus itself?
> > Have you tried commenting it out? Should be in /etc/X11 or
> > somewhere in the session files installed by lightdm.
> >
>
> There's only one dbus user daemon. I have
On 22.01.2016 23:19, Armin K. wrote:
> Hi,
>
> I have a following problem on my system and it has been bothering me for some
> time.
>
> I use KDE Plasma 5 and lightdm as a display manager to login to the session.
> Once
> logged in, the lightdm (I guess it's using pam_systemd.so) login service
On 23.01.2016 00:17, Kai Krakow wrote:
> Am Fri, 22 Jan 2016 23:19:11 +0100
> schrieb "Armin K." :
>
>> I use KDE Plasma 5 and lightdm as a display manager to login to the
>> session. Once logged in, the lightdm (I guess it's using
>> pam_systemd.so) login service will also start systemd user sess
Am Fri, 22 Jan 2016 23:19:11 +0100
schrieb "Armin K." :
> I use KDE Plasma 5 and lightdm as a display manager to login to the
> session. Once logged in, the lightdm (I guess it's using
> pam_systemd.so) login service will also start systemd user session
> and a session dbus daemon. The rest of Pla
On 22.01.2016 23:35, Kai Krakow wrote:
> Am Fri, 22 Jan 2016 23:19:11 +0100
> schrieb "Armin K." :
>
>> I have a following problem on my system and it has been bothering me
>> for some time.
>>
>> I use KDE Plasma 5 and lightdm as a display manager to login to the
>> session. Once logged in, the l
Am Fri, 22 Jan 2016 23:19:11 +0100
schrieb "Armin K." :
> I have a following problem on my system and it has been bothering me
> for some time.
>
> I use KDE Plasma 5 and lightdm as a display manager to login to the
> session. Once logged in, the lightdm (I guess it's using
> pam_systemd.so) logi
Hi,
I have a following problem on my system and it has been bothering me for some
time.
I use KDE Plasma 5 and lightdm as a display manager to login to the session.
Once
logged in, the lightdm (I guess it's using pam_systemd.so) login service will
also
start systemd user session and a session
On Fri, Jan 22, 2016 at 11:47 PM, David Timothy Strauss <
da...@davidstrauss.net> wrote:
> On Fri, Jan 22, 2016 at 1:36 PM Mantas Mikulėnas
> wrote:
>
>> There's a third way:
>>
>> ExecStart=/usr/bin/strace -D -ff -o /tmp/myservice.trace
>> /usr/bin/myservlce --foo
>>
>
> Do you know if that woul
On Fri, Jan 22, 2016 at 1:36 PM Mantas Mikulėnas wrote:
> There's a third way:
>
> ExecStart=/usr/bin/strace -D -ff -o /tmp/myservice.trace
> /usr/bin/myservlce --foo
>
Do you know if that would pass through file descriptors for socket
activation?
___
On Fri, Jan 22, 2016 at 11:17 PM, David Timothy Strauss <
da...@davidstrauss.net> wrote:
> Rebooting an old thread now that we're finally testing this out.
>
> > "strace" should do the job. It should give you a pretty good idea of all
> syscalls a process uses. That's what I used when testing Sysc
Rebooting an old thread now that we're finally testing this out.
> "strace" should do the job. It should give you a pretty good idea of all
syscalls a process uses. That's what I used when testing SyscallFilters=.
This turns out to be less useful than it seems.
There are two major ways to invoke
On Fri, Jan 22, 2016 at 1:55 PM, Jonathan Dowland <
jon+systemd-de...@alcopop.org> wrote:
> Hi, [please CC me on replies if possible],
>
> I have several LUKS-encrypted volumes, upon which I have placed LVM PVs.
> Prior to systemd, I would define them in /etc/crypttab. Right now, due
> to systemd-
Hi, [please CC me on replies if possible],
I have several LUKS-encrypted volumes, upon which I have placed LVM PVs.
Prior to systemd, I would define them in /etc/crypttab. Right now, due
to systemd-cryptsetup-generator, this gets interpreted and translated
into systemd units.
I am wondering wheth
I havn't tried on systemd 222. But, I think the problem is pretty easy to
reproduce and if the code around StandardInput option has not much changed,
then it should reproducible easily even on systemd222.
On Thu, Jan 21, 2016 at 10:37 PM, Chris Morgan wrote:
>
> On Thu, Jan 21, 2016 at 11:59 AM
On 22 January 2016 at 10:38, Colin Guthrie wrote:
...
>> On Fri, 15.01.16 10:33, Igor Bukanov (i...@mir2.org) wrote:
>>> I suppose I already can do with service ExecStartPost, ExecStart hooks
>>> for resolved, but this is rather hackish as I do not know if resolved
>>> updates the file in place (w
Lennart Poettering wrote on 15/01/16 13:36:
> On Fri, 15.01.16 10:33, Igor Bukanov (i...@mir2.org) wrote:
>
>> Hi,
>>
>> currently if one runs systemd-resolved, then /etc/resolv.conf should
>> be symlinked to /run/systemd/resolve/resolv.conf . Is it possible
>> instead to add an option for resol
19 matches
Mail list logo