be nice to double check...
Regards,
Vlad.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unfortunately with systemd-227 the behaviour hasn't been changed.
Vladimir.
On 21/10/15 13:26, Vlad wrote:
> Thanks for the explanation. I'll try 227 asap.
>
> Vladimir.
>
> On 20/10/15 12:19, Lennart Poettering wrote:
>> On Tue, 20.10.15 08:21, Vlad (vo...@vovan.nl
\x2dbacklight.slice.
However I can start/stop service manually and the backlight is properly
restored/saved in /var/lib/systemd/backlight/pci...
I'd appreciate any ideas (running systemd-226).
Regards,
Vlad.
___
systemd-devel mailing list
systemd-devel
red failed state.
Works fine with systemd versions < 234.
Regards,
Vlad.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
at step PAM
spawning /usr/lib/systemd/systemd: Operation not permitted
Apr 29 11:09:37 xxx systemd[1]: Started User Manager for UID xxx.
I'd appreciate any thoughts about this issue.
Regards,
Vlad.
___
systemd-devel mailing list
systemd-devel
Lennart,
As I can see pam_systemd is "optional" everywhere in pam.d
configuration. Is that what you meant?
grep pam_systemd *
system-auth:session optionalpam_systemd.so debug
systemd-user:session optional pam_systemd.so
Regards,
Vlad.
On 29/04/17 12:21, Lennart Poette
I enabled debug for pam_systemd, but it doesn't give useful
information in my case.
Regards,
Vlad.
On 29/04/17 12:21, Lennart Poettering wrote:
> On Sat, 29.04.17 11:13, Vlad (vo...@vovan.nl) wrote:
>
>> Hello,
>>
>> I've recently updated systemd and now user session is fa
the right logic, please correct me it's not the case.
However the first one is just wrong, isn't it?
Regards,
Vlad.
On 29/04/17 18:19, Lennart Poettering wrote:
> On Sat, 29.04.17 16:59, Vlad (vo...@vovan.nl) wrote:
>
>> Thanks for the answer. I'd then rephrase my original question: I'd lik
successfully (pam configuration is exactly the same for
both systemd versions).
Regards,
Vlad.
On 29/04/17 13:29, Lennart Poettering wrote:
> On Sat, 29.04.17 13:25, Vlad (vo...@vovan.nl) wrote:
>
>> Lennart,
>>
>> I've just tried your suggestion as well, but it doesn't chan
Without the x-systemd.automount option just "mount /mnt/data" works fine
after reboot.
Regards,
Vlad.
On 31/07/17 16:36, Lennart Poettering wrote:
> On Do, 27.07.17 12:27, Vlad (vo...@vovan.nl) wrote:
>
>> Hello,
>>
>> Autogenerated from fstab mount unit fails,
nly_
thing that has been changed in the system is the version of installed
systemd and this leads to failed user@xxx.service.
Vlad.
On 29/04/17 18:19, Lennart Poettering wrote:
> On Sat, 29.04.17 16:59, Vlad (vo...@vovan.nl) wrote:
>
>> Thanks for the answer. I'd then rephrase my origi
: files ldap
group: files ldap
hosts: files mymachines dns
===
I'd appreciate any thoughts about this issue.
Regards,
Vlad.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org
systemd users
Do you think changing "DynamicUser" to "no" should solve the issue? I
see that quite a few services (systemd-resolve, systemd-networkd,
firewalld, etc.) have "DynamicUser=yes".
Regards,
Vlad.
On 04/07/18 13:03, Lennart Poettering wrote:
>
with sssd). If
somebody has any experiences in this area, please share ;-)
Regards,
Vlad.
On 04/07/18 13:50, Mantas Mikulėnas wrote:
> On Wed, Jul 4, 2018 at 2:03 PM Lennart Poettering
> mailto:lenn...@poettering.net>> wrote:
>
> I am pretty sure it's not the best design today tha
Hi,
I have Debian Testing running with some additional packages from Linux Mint
which are installed for testing purposes.
One of them is mintsystem, which causes an ordering cycle during the boot:
авг 14 13:51:06 jessica systemd[1]: Found ordering cycle on basic.target/start
авг 14 13:51:06
Hi again,
Thank you all, removing dbus from the prerequisites did the trick.
No more ordering cycles and mintsystem still runs fine.
It turned out that mintsystem didn't even require dbus to work. Must be
a copy-paste mistake (from some other init script) by the author...
As for the
ld Wayland compositors handle logind restarts in
any way?
At the moment, many Wayland compositors don't take any precautions
against the case where logind is restarted. They assume that the DRM
file descriptors will remain valid and the session will be restored
auto-magically.
Ch
es cleanup. It's on the TODO list.
[1] https://github.com/systemd/systemd/pull/17558
Oh, nice. Thank you for clarifying things. :-)
Cheers,
Vlad
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.o
18 matches
Mail list logo
