04.07.2016 21:32, Chris Murphy пишет:
> I have a system where I get an indefinite
>
> "A start job is running for dev-vda2.device (xmin ys / no limit)"
>
> Is there a boot parameter to use to change the no limit to have a
> limit? rd.timeout does nothing.
It should. Use rd.break and examine
On Tue, Jul 05, 2016 at 01:15:30AM +0200, Michał Zegan wrote:
> Hello.
>
> There is a problem with current audit support in journald. it listens
> for audit events, but those same audit events go to dmesg, making a lot
> of garbage.
There were patches for the kernel to not log to dmesg when
Hello.
There is a problem with current audit support in journald. it listens
for audit events, but those same audit events go to dmesg, making a lot
of garbage.
Also, in case of a selinux enabled system, it generates huge amount of
audit output even if you do not want that, for example, pam
On Mon, Jul 04, 2016 at 10:01:48PM +0200, Martin Pitt wrote:
> Hello all,
>
> a while ago I started experimenting with converting Ubuntu's upstart
> graphical session to the user D-Bus and systemd session. This works
> nicely and naturally for services which don't need $DISPLAY and are
> not
Hello Jóhann,
Jóhann B. Guðmundsson [2016-07-04 20:53 +]:
> Shipping an predefined desktop units arguably does not belong upstream since
> it's just catering to one ( desktop ) out of three (
> embedded/server/desktop) target user base.
Right, embedded/server would never start this new unit.
On 07/04/2016 08:01 PM, Martin Pitt wrote:
Feedback appreciated!
Shipping an predefined desktop units arguably does not belong upstream
since it's just catering to one ( desktop ) out of three (
embedded/server/desktop) target user base. It might result in other two
target user base
I have a system where I get an indefinite
"A start job is running for dev-vda2.device (xmin ys / no limit)"
Is there a boot parameter to use to change the no limit to have a
limit? rd.timeout does nothing. When I use rd.break=pre-mount and use
blkid, /dev/vda2 is there and can be mounted with
>-Ursprüngliche Nachricht-
>Von: Lennart Poettering [mailto:lenn...@poettering.net]
>Betreff: Re: [systemd-devel] How to mount NFS prior to start postgresql from
>this volume
>
>Normally, if you want a service to run only after all NFS mounts are in place,
>add an ordering dependency
