On Mon, Dec 3, 2012 at 1:50 AM, Shawn Landden wrote:
> Fix the fallowing error when no system dbus available:
Applied.
Thanks,
Kay
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-
Fix the fallowing error when no system dbus available:
Failed to get system D-Bus connection: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
process 14920: arguments to dbus_connection_close() were incorrect, assertion
"connection != NULL" failed in file .
On Sun, Dec 2, 2012 at 6:06 PM, David Herrmann
wrote:
> If the system does not have any active console, we should not try to
> create an empty symlink. Instead, create no symlink at all.
>
> Otherwise, on systems with CONFIG_VT=n and no serial console, we will
> create a symlink with an empty temp
If the system does not have any active console, we should not try to
create an empty symlink. Instead, create no symlink at all.
Otherwise, on systems with CONFIG_VT=n and no serial console, we will
create a symlink with an empty template parameter.
Signed-off-by: David Herrmann
---
src/getty-g
David Strauss wrote:
> We could also move more tools outside the main systemd package and
> into PIP.
Er, you want to move some essential systemd scripts out from the source tree?
Ram
___
systemd-devel mailing list
[email protected]
ht
Hi Michael,
Michael Biebl wrote:
> 2012/12/2 Ramkumar Ramachandra :
>> Hm, you have a point. On Debian, "/etc/machine-id" is created when
>> the systemd package is installed -- I'm not sure if it's in the source
>> code or if it's a custom Debian patch.
>
> We run systemd-machine-id-setup in post
2012/12/2 Ramkumar Ramachandra :
> Hm, you have a point. On Debian, "/etc/machine-id" is created when
> the systemd package is installed -- I'm not sure if it's in the source
> code or if it's a custom Debian patch.
We run systemd-machine-id-setup in postinst.
Michael
[1]
http://anonscm.debian
Hello list,
some socket activated service gave me the error message you can see on
the subject, maybe systemd should be more verbose in that case. Please
see attached patch (untested).
Thanks,
Dimitris
P.S. Please CC me in all replies.
--- socket.c 2012-12-02 01:53:35.961437348 +0200
+++ socket
Zbigniew Jędrzejewski-Szmek wrote:
> I started munging your patch to apply it, but on second thought it is
> totally the wrong direction to take. The purpose of tests is to check
> if systemd will function after installation. And as mentioned
> elsewhere in the thread, journald will break badly, an
David Strauss wrote:
> Would it be possible, for testing purposes, to generate a machine ID
> on the fly if one is not present on disk?
Hard, as "/etc/machine-id" is hardcoded in
src/libsystemd-id128/sd-id128.c. I don't think it's worth the effort.
Ram
___
On Sat, Dec 01, 2012 at 08:28:43PM -0800, David Strauss wrote:
> Would it be possible, for testing purposes, to generate a machine ID
> on the fly if one is not present on disk?
For systemd to boot properly when the root fs is readonly, either
/etc/machine-id with some value, or an empty /etc/machi
On Sun, Dec 02, 2012 at 02:03:32PM +0400, Dmitry V. Levin wrote:
> On Sat, Dec 01, 2012 at 08:29:42PM -0800, David Strauss wrote:
> > Why not just run rsyslog on whatever sockets you'd like and have it
> > all forward (using syslog protocol) to the journal socket?
>
> Listening on multiple sockets
On Sun, Dec 2, 2012 at 2:03 AM, Dmitry V. Levin wrote:
> Listening on multiple sockets is almost as simple to implement as
> listening a single socket, so isn't it an overkill to run yet another
> syslog daemon just to address this simple issue?
You're welcome to propose a patch. I assume it woul
On Sat, Dec 01, 2012 at 08:29:42PM -0800, David Strauss wrote:
> Why not just run rsyslog on whatever sockets you'd like and have it
> all forward (using syslog protocol) to the journal socket?
Listening on multiple sockets is almost as simple to implement as
listening a single socket, so isn't it
14 matches
Mail list logo
