I suppose you meant pam_keyinit, not pam_keyring, right? Although I saw
that the new version of default "systemd-user" pam configuration file
added pam_keyinit, I tested migration of systemd from 232 to 233 with
exactly the same pam.d configuration (as I mentioned below). The _only_
thing that has
On Sun, 30 Apr 2017, Lennart Poettering wrote:
On Sat, 29.04.17 22:04, Michael Chapman (m...@very.puzzling.org) wrote:
We can't really do that in the generic case, sorry. The distinction
between local-fs.target and remote-fs.target mostly exists because the
latter may rely on network management
Hello everybody,
I have read in a phoronix article that iwd will be integraded into
systemd-networkd.[1] Is this already the case with the newest systemd
version? If not, are there any plans to integrate it into
systemd-networkd? I am really interested in this topic, because
currently I use systemd
On Sat, Apr 29, 2017 at 11:40:44AM +0200, Lennart Poettering wrote:
> That said, there are limits to this: this will only work correctly if
> the start jobs for both units are either enqueued at the same time or
> in the order they are supposed to be run in. If however, the job for
> the unit that
On Sat, Apr 29, 2017 at 08:59:57AM -0500, Dan Nicholson wrote:
> It seems to me that this could be easily around by adding
> Wants=apt-daily.service to the upgrade unit. That will guarantee that
> systemd puts the update job in the queue before the upgrade job. I think
> this is what you want, anyw
Great, thanks!
Lennart Poettering schrieb am Sa., 29. Apr. 2017,
19:32:
> On Wed, 26.04.17 11:08, Benno Fünfstück (benno.fuenfstu...@gmail.com)
> wrote:
>
> > > I have the problem that I want to run a set of services that are
> isolated
> > > from the other services. In particular, I'd like to:
Hi!
I'm struggling to understand if this can be done: suppose i start polling
on sd_bus_get_fd() without any match; then, after some event happens, i add
a match on same bus.
Will i receive events on my fd just going on polling?
Ie: will this work?
fd = sd_bus_get_fd();
event_happened = 0;
poll(fd)
On Wed, 26.04.17 11:08, Benno Fünfstück (benno.fuenfstu...@gmail.com) wrote:
> > I have the problem that I want to run a set of services that are isolated
> > from the other services. In particular, I'd like to:
> >
> > * share some environment variables between these services, that aren't
> > ava
On Wed, 26.04.17 11:05, Benno Fünfstück (benno.fuenfstu...@gmail.com) wrote:
> Hi,
>
> I have the problem that I want to run a set of services that are isolated
> from the other services. In particular, I'd like to:
>
> * share some environment variables between these services, that aren't
> ava
On Wed, 26.04.17 10:09, prashantkumar dhotre (prashantkumardho...@gmail.com)
wrote:
> Hi
> For my service, I have:
>
> # cat my.service
> [Unit]
> Description=My Service
> After=dbus.service
> Requires=dbus.service
> ...
> ...
>
> Some time i see that my service fails to get dbus connection
>
On Sat, 29.04.17 22:04, Michael Chapman (m...@very.puzzling.org) wrote:
> > We can't really do that in the generic case, sorry. The distinction
> > between local-fs.target and remote-fs.target mostly exists because the
> > latter may rely on network management services which aren't available
> > i
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 like
> to know what has been changed in the systemd (pam_systemd?) version 233,
> that now it fails to start user@xxx.service? If I downgrade to the
> version 232, then systemd
Thanks for the answer. I'd then rephrase my original question: I'd like
to know what has been changed in the systemd (pam_systemd?) version 233,
that now it fails to start user@xxx.service? If I downgrade to the
version 232, then systemd gives the same error, but still starts
user@xxx.service succe
On Apr 27, 2017 4:31 PM, "Julian Andres Klode" wrote:
Hi systemd folks,
(service and timer files being discussed at the bottom)
we are currently reworking the way automatic updates and upgrades work
on Ubuntu and Debian systems. We basically have two persistent timers
with associated services:
On Sat, 29 Apr 2017, Lennart Poettering wrote:
On Thu, 27.04.17 15:53, Michael Chapman (m...@very.puzzling.org) wrote:
Hello all,
At present, when systemd-fstab-generator creates an automount unit for an
fstab entry, it applies the dependencies that would have been put into the
mount unit into
On Tue, 25.04.17 16:05, Jeremy Eder (je...@redhat.com) wrote:
> Sorry, I did not explain myself clearly. systemd is doing nothing wrong.
> What I'd like to do is find an optimal way to notify our monitoring system
> (zabbix) that a service is flapping. We can probably script something.
> Just lo
On Tue, 25.04.17 11:30, Jeremy Eder (je...@redhat.com) wrote:
> If we have a service that is flapping because it's crashing after
> startup...what's the right way to monitor for that condition? Eventually
> it triggers startburstlimit, was thinking that if we hit startburstlimit
> that the servic
On Tue, 25.04.17 11:28, Daniel Wang (wonder...@google.com) wrote:
> Hi all,
>
> First of all this is my first email to this list so apologies if it's not
> worded perfectly.
>
> I am wondering if there's any plan to support Domain Search List option in
> networkd. Some cloud providers like GCE,
On Fri, 28.04.17 09:36, Michal Sekletar (msekl...@redhat.com) wrote:
> Hi,
>
> On big setups (read: a lot of multipathed disks), probing and
> assembling storage may take significant amount of time. However, by
> default systemd waits only 90s (DefaultTimeoutStartSec) for
> "top-level" device uni
Linux-PAM supports -prefix everywhere, but it simply means "ignore
nonexistent modules instead of warning". (Therefore it doesn't make sense
on distros where pam_systemd is guaranteed to exist.)
However, the dash prefix never ignores errors returned by the module itself
– that's what the 'optional
On Thu, 27.04.17 15:53, Michael Chapman (m...@very.puzzling.org) wrote:
> Hello all,
>
> At present, when systemd-fstab-generator creates an automount unit for an
> fstab entry, it applies the dependencies that would have been put into the
> mount unit into the automount unit instead.
>
> For a
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 change behavior.
> I'm just wondering how it would be possible to investigate the error.
> The message "user@xxx.service: Failed at step PAM spawning
> /usr/lib/systemd/syst
Lennart,
I've just tried your suggestion as well, but it doesn't change behavior.
I'm just wondering how it would be possible to investigate the error.
The message "user@xxx.service: Failed at step PAM spawning
/usr/lib/systemd/systemd: Operation not permitted" isn't very
descriptive. I enabled de
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 Poettering wrote:
> On
On Thu, 27.04.17 12:52, jr (darwinsker...@gmail.com) wrote:
> On Wed, Apr 26, 2017 at 04:08:21PM +0200, Lennart Poettering wrote:
> > On Tue, 25.04.17 13:13, jr (darwinsker...@gmail.com) wrote:
> >
> > > hello,
> > >
> > > in a fully-volatile boot scenario /usr from a physical disk gets mounted
On Sat, 29.04.17 11:13, Vlad (vo...@vovan.nl) wrote:
> Hello,
>
> I've recently updated systemd and now user session is failing to start:
> Apr 29 11:04:02 xxx systemd[550]: user@xxx.service: Failed at step PAM
> spawning /usr/lib/systemd/systemd: Operation not permitted
> Apr 29 11:04:02 xxx sys
On Thu, 27.04.17 23:30, Julian Andres Klode (j...@debian.org) wrote:
> Hi systemd folks,
>
> (service and timer files being discussed at the bottom)
>
> we are currently reworking the way automatic updates and upgrades work
> on Ubuntu and Debian systems. We basically have two persistent timers
Hello,
I've recently updated systemd and now user session is failing to start:
Apr 29 11:04:02 xxx systemd[550]: user@xxx.service: Failed at step PAM
spawning /usr/lib/systemd/systemd: Operation not permitted
Apr 29 11:04:02 xxx systemd[1]: Failed to start User Manager for UID xxx.
Apr 29 11:04:02
28 matches
Mail list logo
