Michael Biebl wrote:
2012/11/30 Ramkumar Ramachandra artag...@gmail.com:
Execute python using /usr/bin/env python instead of hard-coding the
I'm not really a fan of using /usr/bin/env, as you can pick up a
random python version depending on how your PATH is setup.
Besides, you need to spawn
On Fri, Nov 30, 2012 at 2:28 PM, Khem Raj raj.k...@gmail.com wrote:
I have a scenario where, I have foo.service which runs on boot and later
bar.service runs and it has to stop foo.service which I achieved by
declaring it as Conflicts= in the unit file but I would like to restart
foo.service
David Strauss wrote:
Please fix the spelling of present.
The number -128, if used, should get #define'd instead of being a magic
number dropped in a bunch of places.
Thanks. Will fix in the next iteration.
It's not good to mask all errors opening the machine-id with the -128
response code.
Hi,
I booted up my Debian machine with systemd, and removed systemd after
bootup. Now it refuses to halt with:
init: timeout opening/writing control channel /dev/initctl
I don't know if it's systemd's fault or the Debian package manager's
fault- investigating.
Ram
Ramkumar Ramachandra wrote:
I booted up my Debian machine with systemd, and removed systemd after
bootup. Now it refuses to halt with:
init: timeout opening/writing control channel /dev/initctl
Correction: I can't halt a Debian systemd machine at all (even when
the package isn't removed)!
On Fri, Nov 30, 2012 at 3:53 PM, David Strauss da...@davidstrauss.netwrote:
On Fri, Nov 30, 2012 at 2:28 PM, Khem Raj raj.k...@gmail.com wrote:
I have a scenario where, I have foo.service which runs on boot and later
bar.service runs and it has to stop foo.service which I achieved by
We could also move more tools outside the main systemd package and
into PIP. PIP alters the top of any registered Python executable to
use the version of Python corresponding to the version of PIP used to
install it. Fedora packages both Python 2.7 and Python 3.2/3.3 PIP
clients.
On Fri, Nov 30,
The following tests fail if /etc/machine-id is not present:
$ ./test-id128
random: a08ea8ed34594d4bbd953dd182ec86f9
Assertion 'sd_id128_get_machine(id) == 0' failed at
src/test/test-id128.c:41, function main(). Aborting.
[1]8017 abort (core dumped) ./test-id128
$ ./test-journal
On Fri, Nov 30, 2012 at 3:59 AM, Colin Guthrie gm...@colin.guthr.ie wrote:
It won't give you all the features above it should mean that no connections
are lost in that window.
I don't think socket activation will do that. If systemd has spawned a
process for each connection, those will get
Hi,
On Sun, Nov 25, 2012 at 12:19:27AM +0100, Lennart Poettering wrote:
[...]
Currently, journald cannot listen on multiple syslog sockets (though we
could certainly add that).
A simple alternative could be to just make /var/lib/ldap/dev/log
symlinks? If you are using chroots and these
A few things:
- Please fix the spelling of present.
- The number -128, if used, should get #define'd instead of being a
magic number dropped in a bunch of places.
- It's not good to mask all errors opening the machine-id with the -128
response code. The change here seems to make
yeah OnStop= and/or OnShutdown= is something that will solve my problem
exactly
You can try this one:
http://lists.freedesktop.org/archives/systemd-devel/2012-November/007304.html
// wbr, Alex
___
systemd-devel mailing list
On Sat, Dec 01, 2012 at 10:01:35AM +0530, Ramkumar Ramachandra wrote:
The following tests fail if /etc/machine-id is not present:
$ ./test-id128
random: a08ea8ed34594d4bbd953dd182ec86f9
Assertion 'sd_id128_get_machine(id) == 0' failed at
src/test/test-id128.c:41, function main().
El 01/12/12 01:26, Ramkumar Ramachandra escribió:
Hi,
I booted up my Debian machine with systemd, and removed systemd after
bootup. Now it refuses to halt with:
init: timeout opening/writing control channel /dev/initctl
I don't know if it's systemd's fault or the Debian package manager's
On Fri, Nov 30, 2012 at 01:36:05PM +0100, Eelco Dolstra wrote:
---
man/udevadm.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Applied.
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
]] Ramkumar Ramachandra
I booted up my Debian machine with systemd, and removed systemd after
bootup. Now it refuses to halt with:
You shouldn't have been able to do this. I'm adding a patch to the
Debian package to prevent this from happening in the future.
--
Tollef Fog Heen
UNIX is
Hello,
How does systemd kill the running processes at shutdown?
(I tried asking at fedoraforum.org first, but got no responses there.)
Presumably it tries to gracefully stop all services. Is every process part of a
service?
When it stops a service, it presumably runs the ExecStop of that
Am 01.12.2012 16:20, schrieb tom289...@safe-mail.net:
How does systemd kill the running processes at shutdown?
(I tried asking at fedoraforum.org first, but got no responses there.)
Presumably it tries to gracefully stop all services. Is every process part of
a service?
finally each
---
DISTRO_PORTING | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/DISTRO_PORTING b/DISTRO_PORTING
index a6ae043..7702990 100644
--- a/DISTRO_PORTING
+++ b/DISTRO_PORTING
@@ -9,7 +9,7 @@ HOWTO:
insensitively) and you should be able to find the places where
On Sat, Dec 1, 2012 at 4:20 PM, tom289...@safe-mail.net wrote:
How does systemd kill the running processes at shutdown?
On Sat, Dec 1, 2012 at 6:59 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 01.12.2012 16:20, schrieb tom289...@safe-mail.net:
How does systemd kill the running
2012/12/1 Ramkumar Ramachandra artag...@gmail.com:
Ramkumar Ramachandra wrote:
I booted up my Debian machine with systemd, and removed systemd after
bootup. Now it refuses to halt with:
init: timeout opening/writing control channel /dev/initctl
Can you try
ls -la /dev/initctl /run/initctl
On Sat, Dec 1, 2012 at 2:27 PM, yannicklm yannicklm1...@gmail.com wrote:
---
DISTRO_PORTING | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
I think that was fixed yesterday already:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=7830fcd836fb1e8901a534da9ae733109eeba9c4
On Sat, Dec 1, 2012 at 6:52 AM, Oleksii Shevchuk alx...@gmail.com wrote:
yeah OnStop= and/or OnShutdown= is something that will solve my problem
exactly
You can try this one:
http://lists.freedesktop.org/archives/systemd-devel/2012-November/007304.html
exactly what I needed. Thanks.
Would it be possible, for testing purposes, to generate a machine ID
on the fly if one is not present on disk?
On Sat, Dec 1, 2012 at 7:48 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sat, Dec 01, 2012 at 10:01:35AM +0530, Ramkumar Ramachandra wrote:
The following tests fail if
Why not just run rsyslog on whatever sockets you'd like and have it
all forward (using syslog protocol) to the journal socket?
On Sat, Dec 1, 2012 at 6:09 AM, Dmitry V. Levin l...@altlinux.org wrote:
Hi,
On Sun, Nov 25, 2012 at 12:19:27AM +0100, Lennart Poettering wrote:
[...]
Currently,
Unfortunately, I don't think that patch is going in as-is. Lennart is
worried about it bloating the unit configuration language and
increasing the chance of a loop.
The change of adding OnStop= wouldn't bother me, but I don't feel
strongly enough to take it up as a cause. You should join the
26 matches
Mail list logo
