Lennart,
I think I found another clue. I noticed that the directory
/var/log/journal was being used in addition to /var/run/log/journal. I
do not want persistent logging, so I removed /var/log/journal. When I
did this, systemd-journalctl appeared to work correctly.
Obviously I am mis-un
Hello,
I'm debugging a systemd shutdown problem where systemd hangs. I would like
to track the shutdown process - presumably using log_error() all over the
place.
What is the best-practices development cycle for testing changes to the
source? Do you use a VM and if so, do you build an RPM (or wha
Le lundi 26 mars 2012 à 18:51 +0200, Lennart Poettering a écrit :
> On Mon, 26.03.12 14:25, Frederic Crozat ([email protected]) wrote:
...
> Need to handle OOM. memdup() might be nicer to use here. (In fact, might
> be worth introducing newdup() here as a type-safe macro, i.e. a
> combination of new
On Fri, 30.03.12 14:48, Ayoub Arfaoui ([email protected]) wrote:
> How to patch a service to be socket-activable ?
http://0pointer.de/blog/projects/socket-activation.html
http://0pointer.de/blog/projects/socket-activation2.html
This is all linked from the systemd homepage BTW.
http://www.free
On Fri, Mar 30, 2012 at 02:48:03PM +0100, Ayoub Arfaoui wrote:
> How to patch a service to be socket-activable ?
http://0pointer.de/blog/projects/socket-activation.html
http://0pointer.de/blog/projects/socket-activation2.html
--
Tomasz TorczTo co nierealne -- tutaj
How to patch a service to be socket-activable ?
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Mar 30, 2012 at 04:44, Jean-Luc Duprat wrote:
> My system has an ext4 filesystem with 4K blocks, so I need to pass the -b
> 32768 option e2fsck when I check it.
>
> When systemd-fsck attempts to check that filesystem, it doesn't pass the
> appropriate flag; as a result the fail checks and
My system has an ext4 filesystem with 4K blocks, so I need to pass the -b
32768 option e2fsck when I check it.
When systemd-fsck attempts to check that filesystem, it doesn't pass the
appropriate flag; as a result the fail checks and the boot process stops.
How do I teach systemd-fsck how to check
