On Wednesday 2013-11-20 12:36, Tom Gundersen wrote:
>>> [Network]
>>> Address=192.168.0.1/24
>>> Address=192.168.0.2/24
>>> Gateway=192.168.1.1
>>>
>>> [Address:oneaddress]
>>> Address=192.168.0.3/24
>>> Label=three
>>> Peer=192.168.1.1
>>
>> Arent's we sacrificing significant part of simplicity i
I have been getting that since before this specific patch. host:
debian sid systemd v204, target arch with HEAD systemd
On Wed, Nov 20, 2013 at 2:10 PM, Tom Gundersen wrote:
> On Wed, Nov 20, 2013 at 9:08 PM, Lennart Poettering
> wrote:
>> Heya!
>>
>> I just pushed a huge patch that ports the la
On 2013-11-21, 13:14 +1000, David Timothy Strauss wrote:
> I often get this when I have a dirty build. Have you tried a fully clean
> build?
Retried with a make distclean, and you're right, do not met this issue
again.
So please ignore this patch.
Regards,
Kangkai
__
Thanks David
The trick you suggested for point 3 may not work in my case. What happens
is - my process may be busy with some other activity during which time it
will fail to send periodic message to systemd. After a while it will come
out of it's loop and ready to serve. But during this time syste
Hey Lennart,
Lennart Poettering [2013-11-21 0:16 +0100]:
> On Thu, 14.11.13 07:45, Martin Pitt (martin.p...@ubuntu.com) wrote:
>
> > Hello all,
> >
> > pam_systemd currently causes some havoc when you run programs or
> > shells with su: it passes on the $XDG_RUNTIME_DIR from the original
> > us
On Thu, Nov 21, 2013 at 4:33 PM, salil GK wrote:
> 3. One more use case I can think of is - if the process fail to send
> heartbeat message ( WATCHDOG ) for some time and later it starts sending -
> because of some time. So during the time WATCHDOG notification is missing
> process can be mark
Thanks David and Zbyszek
Yes with BindsTo parameter it works
David
I was trying out the options in the unit file hence PID parameter came
in. I forgot to remove that later :-(
some more questions in the same thread -
1. How do I trace the heartbeat message - or rather can I capture th
]] Lennart Poettering
> Well, that's quite arbitrary. What about dbus, X11, and so on, do you
> plan to turn that off for the new session too?
Yes, please.
In the following, I'm talking about «su -» not plain «su», which I think
should go away since the semantics are woolen.
> su is a hack, it
The service configuration is strange. Normally, this is how they work
with dependencies:
* Type=simple considers the service started immediately on exec()
with no respect for PIDFiles or sd_notify. This can cause dependent
services to come up too early.
* Type=forking considers the service start
I often get this when I have a dirty build. Have you tried a fully clean build?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Otherwise, build fail:
/usr/bin/ld: ./.libs/libsystemd-daemon-internal.a(sd-daemon.o): undefined
reference to symbol 'mq_getattr@@GLIBC_2.3.4'
/usr/bin/ld: note: 'mq_getattr@@GLIBC_2.3.4' is defined in DSO /lib/librt.so.1
so try adding it to the linker command line
/lib/librt.so.1: could not rea
On Thu, Nov 21, 2013 at 11:48 AM, David Timothy Strauss
wrote:
> This would be particularly useful for bridges.
Actually, I meant bonded interfaces, not bridges.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop
Just to suggest the wildly different approach I mentioned on IRC, we
could treat addresses (including DHCP) as the main units and then
specify the backing hardware as part of the address's configuration.
This would be particularly useful for bridges.
___
On Thu, Nov 21, 2013 at 2:39 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Thu, Nov 21, 2013 at 02:27:28AM +0100, Tom Gundersen wrote:
>> On Wed, Nov 20, 2013 at 10:37 PM, Lennart Poettering
>> wrote:
>> > On Wed, 20.11.13 14:38, Tom Gundersen (t...@jklm.no) wrote:
>> >
>> >> Pass on the line on wh
On Thu, Nov 21, 2013 at 02:27:28AM +0100, Tom Gundersen wrote:
> On Wed, Nov 20, 2013 at 10:37 PM, Lennart Poettering
> wrote:
> > On Wed, 20.11.13 14:38, Tom Gundersen (t...@jklm.no) wrote:
> >
> >> Pass on the line on which a section was decleared to the parsers, so they
> >> can distinguish bet
On Wed, Nov 20, 2013 at 10:37 PM, Lennart Poettering
wrote:
> On Wed, 20.11.13 14:38, Tom Gundersen (t...@jklm.no) wrote:
>
>> Pass on the line on which a section was decleared to the parsers, so they
>> can distinguish between multiple sections (if they chose to). Currently
>> no parsers take adv
2013/11/21 Michael Biebl :
> Hm, yeah, that might be it.
> I guess one would have to ask the bug reporters if they had used su to
> start a root X application (in case they remember) and if the problem
> goes away after a reboot, i.e. /run has been "reset".
Actually, starting a root X application
2013/11/21 Colin Walters :
> On Thu, 2013-11-21 at 01:20 +0100, Michael Biebl wrote:
>> 2013/11/18 Michael Stapelberg :
>> > This is a rather pressing issue for us (it breaks GDM logins in some
>> > cases), and we’d like to fix it by cherry-picking a patch that was
>> > merged upstream.
>>
>> "some
2013/11/21 Colin Walters :
> On Thu, 2013-11-21 at 01:20 +0100, Michael Biebl wrote:
>> 2013/11/18 Michael Stapelberg :
>> > This is a rather pressing issue for us (it breaks GDM logins in some
>> > cases), and we’d like to fix it by cherry-picking a patch that was
>> > merged upstream.
>>
>> "some
On Thu, 2013-11-21 at 01:20 +0100, Michael Biebl wrote:
> 2013/11/18 Michael Stapelberg :
> > This is a rather pressing issue for us (it breaks GDM logins in some
> > cases), and we’d like to fix it by cherry-picking a patch that was
> > merged upstream.
>
> "some cases" is very vague.
See:
https
On Thu, 2013-11-21 at 00:36 +0100, Lennart Poettering wrote:
> On Tue, 19.11.13 13:13, Colin Walters (walt...@verbum.org) wrote:
>
> > Anyways, new tested patch attached. Lennart, any objections?
>
> Yes. Let's not tape over problems and pretend things could work if we
> freely mix and match thi
2013/11/18 Michael Stapelberg :
> This is a rather pressing issue for us (it breaks GDM logins in some
> cases), and we’d like to fix it by cherry-picking a patch that was
> merged upstream.
"some cases" is very vague. Reading through the gdm bug report (or the
one re-assigned to libpam-systemd) i
On Thu, 2013-11-21 at 00:32 +0100, Lennart Poettering wrote:
> On Tue, 19.11.13 10:42, Colin Walters (walt...@verbum.org) wrote:
>
> > My patch though starts to pave the way for having XDG_RUNTIME_DIR
> > consistently point to that of the user's uid
>
> I think this is just bogus. You used "su".
2013/11/21 Lennart Poettering :
> For that, add a new parameter to pam_systemd maybe
> "force-new-session=yes/no" or so which is set in "su -"'s PAM config
> stack, but not in "su"'s PAM config stack (luckily they are stored in
> two separate files).
This is not the case for Debian based distros,
On Tue, 19.11.13 13:13, Colin Walters (walt...@verbum.org) wrote:
> Anyways, new tested patch attached. Lennart, any objections?
Yes. Let's not tape over problems and pretend things could work if we
freely mix and match things.
I do like Martin's original patch, since by unsetting XDG_RUNTIME_D
On Tue, 19.11.13 10:42, Colin Walters (walt...@verbum.org) wrote:
> My patch though starts to pave the way for having XDG_RUNTIME_DIR
> consistently point to that of the user's uid
I think this is just bogus. You used "su". So the UID was changed and
little else. Now you start patchign XDG_RUNTIM
On Thu, Nov 21, 2013 at 12:06 AM, Lennart Poettering
wrote:
> On Wed, 20.11.13 23:58, Tom Gundersen (t...@jklm.no) wrote:
>
>> >> I tried comparing latest git with v208 in systemd-nspawn.
>>
>> Booting latest git on bare metal I get:
>>
>> Program terminated with signal 11, Segmentation fault.
>>
On Thu, 14.11.13 07:45, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hello all,
>
> pam_systemd currently causes some havoc when you run programs or
> shells with su: it passes on the $XDG_RUNTIME_DIR from the original
> user session, so that programs like pulseaudio or dconf end up
> scribbling
On Wed, 20.11.13 23:58, Tom Gundersen (t...@jklm.no) wrote:
> >> I tried comparing latest git with v208 in systemd-nspawn.
>
> Booting latest git on bare metal I get:
>
> Program terminated with signal 11, Segmentation fault.
> #0 0x7fcc392be74b in raise () from /usr/lib/libpthread.so.0
> (
On Wed, Nov 20, 2013 at 11:44 PM, Lennart Poettering
wrote:
> On Wed, 20.11.13 23:10, Tom Gundersen (t...@jklm.no) wrote:
>
>>
>> On Wed, Nov 20, 2013 at 9:08 PM, Lennart Poettering
>> wrote:
>> > Heya!
>> >
>> > I just pushed a huge patch that ports the last remaining bit from
>> > libdbus to li
On Wed, 20.11.13 23:10, Tom Gundersen (t...@jklm.no) wrote:
>
> On Wed, Nov 20, 2013 at 9:08 PM, Lennart Poettering
> wrote:
> > Heya!
> >
> > I just pushed a huge patch that ports the last remaining bit from
> > libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> > lot of
On Wed, Nov 20, 2013 at 9:08 PM, Lennart Poettering
wrote:
> Heya!
>
> I just pushed a huge patch that ports the last remaining bit from
> libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> lot of code. I did quite a bit of (personal and automated) testing but
> given how la
Hi
On Tue, Nov 19, 2013 at 7:13 PM, Laércio de Sousa wrote:
> Hi there!
>
> I'm testing both Fedora 20 Beta and openSUSE 13.1 in my multiseat system
> (with GNOME 3.10, GDM 3.10.0.1 and systemd 208). I'm currently observing a
> strange behaviour which didn't occur in previous distro release (with
On Tue, 19.11.13 02:33, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Mon, Nov 18, 2013 at 02:48:14PM +0100, Karel Zak wrote:
> > A few trivial patches... the duplications found by
> > https://raw.github.com/karelzak/util-linux/master/tools/checkincludes.pl
> Wow. Applied in one b
On Tue, 19.11.13 14:18, Marcos Felipe Rasia de Mello (marcos...@gmail.com)
wrote:
> Hi folks,
>
> I am trying to disable HDDs power management in a systemd way (aka no
> shell scripts :)
>
> /etc/udev/rules.d/99-hdparm.rules
>
> SUBSYSTEM=="block", KERNEL=="sd*", ATTR{removable}=="0",
> TAG+="
On Wed, 20.11.13 14:38, Tom Gundersen (t...@jklm.no) wrote:
> Pass on the line on which a section was decleared to the parsers, so they
> can distinguish between multiple sections (if they chose to). Currently
> no parsers take advantage of this, but a follow-up patch will do that
> to distinguish
On Tue, 19.11.13 22:28, Colin Guthrie (gm...@colin.guthr.ie) wrote:
>
> 'Twas brillig, and Oleksii Shevchuk at 19/11/13 21:10 did gyre and gimble:
> >> Valgrind
> >
> > Any methodology for pid 1 valgrinding? How to start/gather information
> > for example?
> >
> > Do you have any setup for that
Hi
On Wed, Nov 20, 2013 at 9:18 PM, Lennart Poettering
wrote:
> On Wed, 20.11.13 07:59, David Herrmann (dh.herrm...@gmail.com) wrote:
>
>> If a timer fires and is marked pending, but an application re-arms it
>> before it is dispatched, we now clear the pending state.
>>
>> This fixes a bug where
> I just pushed a huge patch that ports the last remaining bit from
> libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> lot of code. I did quite a bit of (personal and automated) testing but
> given how large this is I am sure I broke something. So, please, be
> careful arou
On Thu, 21.11.13 00:10, Peter Lemenkov (lemen...@gmail.com) wrote:
>
> 2013/11/21 Lennart Poettering :
> > Heya!
> >
> > I just pushed a huge patch that ports the last remaining bit from
> > libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> > lot of code. I did quite a bit
On Thu, Nov 21, 2013 at 12:10:27AM +0400, Peter Lemenkov wrote:
> 2013/11/21 Lennart Poettering :
> > Heya!
> >
> > I just pushed a huge patch that ports the last remaining bit from
> > libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> > lot of code. I did quite a bit of (pe
On Wed, 20.11.13 07:59, David Herrmann (dh.herrm...@gmail.com) wrote:
> If a timer fires and is marked pending, but an application re-arms it
> before it is dispatched, we now clear the pending state.
>
> This fixes a bug where an application arms a timer, which fires and is
> marked pending. But
2013/11/21 Lennart Poettering :
> Heya!
>
> I just pushed a huge patch that ports the last remaining bit from
> libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
> lot of code. I did quite a bit of (personal and automated) testing but
> given how large this is I am sure I brok
Heya!
I just pushed a huge patch that ports the last remaining bit from
libdbus to libsystemd-bus: PID 1 itself. It's a large patch, touching a
lot of code. I did quite a bit of (personal and automated) testing but
given how large this is I am sure I broke something. So, please, be
careful around
On 11/20/2013 07:54 PM, Cecil Westerhof wrote:
Most of the active developers hang out on IRC on freenode #systemd, if
you want to chat instead of writing mails.
That would also be a good idea. I only have two weeks and a lot of
ground to cover.
I had three major problems. I could move them to
Hi,
Looks good generally but two very small points:
'Twas brillig, and Colin Walters at 20/11/13 17:34 did gyre and gimble:
> +/* Ensure the XDG_RUNTIME_DIR for root always exists, so that
> + * su/sudo/pkexec all do the right thing when changing to root.
> + */
> +static int ensure_root_runtime
On 11/20/2013 07:45 PM, Kay Sievers wrote:
I have to give a talk about systemd. My colleges are a ‘little’ negative
about systemd. So I have some questions about systemd. Someone pointed me to
this group, but because of the devel in the name, I was wondering if this
would be the right place to po
On Wed, Nov 20, 2013 at 07:24:18PM +0100, Cecil Westerhof wrote:
> I have to give a talk about systemd. My colleges are a ‘little’
> negative about systemd. So I have some questions about systemd.
> Someone pointed me to this group, but because of the devel in the
> name, I was wondering if this wo
On Wed, Nov 20, 2013 at 7:24 PM, Cecil Westerhof
wrote:
> I have to give a talk about systemd. My colleges are a ‘little’ negative
> about systemd. So I have some questions about systemd. Someone pointed me to
> this group, but because of the devel in the name, I was wondering if this
> would be t
I have to give a talk about systemd. My colleges are a ‘little’ negative
about systemd. So I have some questions about systemd. Someone pointed
me to this group, but because of the devel in the name, I was wondering
if this would be the right place to post that kind of questions.
If you know a
On Tue, 2013-11-19 at 22:38 +, Colin Guthrie wrote:
> 'Twas brillig, and Colin Walters at 19/11/13 18:13 did gyre and gimble:
> > +d /run/user/0 0755 root root 10d
>
> This should probably be 0700 like the runtime dirs usually are I think.
Ooops =/ Fixed!
> Also won't this folder be natural
Hi!
'Twas brillig, and Colin Walters at 20/11/13 14:49 did gyre and gimble:
> On Wed, 2013-11-20 at 10:16 +, Colin Guthrie wrote:
>
>> How do we fix this?
>
> There are a lot of cases - "screen" is just one of them. I think to
> make forward progress on this we'll have to enumerate the case
On Wed, 2013-11-20 at 10:16 +, Colin Guthrie wrote:
> How do we fix this?
There are a lot of cases - "screen" is just one of them. I think to
make forward progress on this we'll have to enumerate the cases,
evaluate the problems with each, then for each problem, evaluate a fix -
and make sur
On Wed, Nov 20, 2013 at 3:05 PM, Thomas Bächler wrote:
> Am 20.11.2013 15:02, schrieb Tom Gundersen:
>>> what does this mean? Does it override the value of the first section,
>>> the second section or does it create a new section?
>>
>> Yeah, in this case it would not make sense. However, this stu
Am 20.11.2013 15:02, schrieb Tom Gundersen:
>> what does this mean? Does it override the value of the first section,
>> the second section or does it create a new section?
>
> Yeah, in this case it would not make sense. However, this stuff is
> opt-in only, and unit files don't opt-in (currently n
On Wed, Nov 20, 2013 at 2:57 PM, Thomas Bächler wrote:
> Am 20.11.2013 14:38, schrieb Tom Gundersen:
>> Pass on the line on which a section was decleared to the parsers, so they
>> can distinguish between multiple sections (if they chose to). Currently
>> no parsers take advantage of this, but a f
Am 20.11.2013 14:38, schrieb Tom Gundersen:
> Pass on the line on which a section was decleared to the parsers, so they
> can distinguish between multiple sections (if they chose to). Currently
> no parsers take advantage of this, but a follow-up patch will do that
> to distinguish
>
> [Address]
>
On Wed, Nov 20, 2013 at 07:09:13PM +0530, salil GK wrote:
> Hello
>
> I am pretty new to systemd.
> I am trying to write two dependent services Myservice and MyserviceTwo.
>
> *Myservice.service*
>
> *[Unit]*
> *Description=This is a test service*
>
> *[Service]*
> *PIDFile=/var/run/Myservi
Hello
I am pretty new to systemd.
I am trying to write two dependent services Myservice and MyserviceTwo.
*Myservice.service*
*[Unit]*
*Description=This is a test service*
*[Service]*
*PIDFile=/var/run/Myservice.pid*
*ExecStartPre=/bin/rm -f /tmp/log.log*
*#ExecStartPre=/usr/bin/systemctl s
On Wed, Nov 20, 2013 at 7:48 AM, Thomas H.P. Andersen wrote:
> Hi Tom,
>
> Sorry. Git send-email is just giving me error messages right now. I
> have attached the patch instead.
Thanks! Applied.
-t
> On Wed, Nov 20, 2013 at 1:12 AM, Tom Gundersen wrote:
>> Hi Thomas,
>>
>> I'm not able to apply
On Wed, Nov 20, 2013 at 12:02 PM, "Jóhann B. Guðmundsson"
wrote:
> On 11/19/2013 09:20 PM, Tom Gundersen wrote:
>>
>> On Tue, Nov 19, 2013 at 7:07 PM, Colin Guthrie
>> wrote:
>> What I have in mind (though it is not dictated by this patch) is
>> something different (first proposed by Lennart in an
On Wed, Nov 20, 2013 at 12:02 PM, "Jóhann B. Guðmundsson"
wrote:
>
> On 11/19/2013 09:20 PM, Tom Gundersen wrote:
>>
>> On Tue, Nov 19, 2013 at 7:07 PM, Colin Guthrie
>> wrote:
>> What I have in mind (though it is not dictated by this patch) is
>> something different (first proposed by Lennart in
On 11/19/2013 09:20 PM, Tom Gundersen wrote:
On Tue, Nov 19, 2013 at 7:07 PM, Colin Guthrie wrote:
What I have in mind (though it is not dictated by this patch) is
something different (first proposed by Lennart in an earlier thread):
[Network]
Address=192.168.0.1/24
Address=192.168.0.2/24
Gate
Hi,
One other thing occurred this morning while pondering the latest patches
from Martin and Colin on this topic.
What should (in an ideal world) apps like screen do?
I have a screen session on my server running a little python irc bot.
I ssh in to the server, start screen, start my bot, detatc
---
src/core/service.c | 3 +--
src/core/service.h | 2 --
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/core/service.c b/src/core/service.c
index c0ee114..24f7a42 100644
--- a/src/core/service.c
+++ b/src/core/service.c
@@ -2812,7 +2812,7 @@ _pure_ static bool service_check_sn
65 matches
Mail list logo
