Ivan Shapovalov gmail.com> writes:
>
> On Wednesday 27 August 2014 at 03:16:10, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Aug 26, 2014 at 10:21:59PM +0200, Lennart Poettering wrote:
> > > On Wed, 27.08.14 00:17, Ivan Shapovalov (intelfx100 gmail.com) wrote:
> > > > This patchset allows
В Thu, 28 Aug 2014 00:31:49 +0300
Mantas Mikulėnas пишет:
> On Aug 27, 2014 10:03 PM, "Dale R. Worley" wrote:
> >
> > > From: Thomas Suckow
> > >
> > > >> From: Lennart Poettering
> > > >
> > > >> Note that a concept of "mount at boot if it is there, otherwise
> don't"
> > > >> cannot work.
>
On Wed, Aug 27, 2014 at 05:07:10PM -0700, Luis R. Rodriguez wrote:
> > Hey, if you have patches already, I'll be glad to look at them :)
>
> OK well I'll spin what I have then, but I'm reviewing Wu's solution
> from February as well. I take it we'd want the async_schedule()
> approach rather that
On Wed, Aug 27, 2014 at 4:44 PM, Greg Kroah-Hartman
wrote:
> On Wed, Aug 27, 2014 at 03:51:58PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Aug 11, 2014 at 10:19 AM, Luis R. Rodriguez wrote:
>> > On Mon, Aug 11, 2014 at 12:57 PM, Lennart Poettering
>> > wrote:
>> >> On Mon, 11.08.14 18:39, Luis R
On Wed, Aug 27, 2014 at 03:51:58PM -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 11, 2014 at 10:19 AM, Luis R. Rodriguez wrote:
> > On Mon, Aug 11, 2014 at 12:57 PM, Lennart Poettering
> > wrote:
> >> On Mon, 11.08.14 18:39, Luis R. Rodriguez ([email protected]) wrote:
> >>
> >>> > This looks reall
On Mon, Aug 11, 2014 at 10:19 AM, Luis R. Rodriguez wrote:
> On Mon, Aug 11, 2014 at 12:57 PM, Lennart Poettering
> wrote:
>> On Mon, 11.08.14 18:39, Luis R. Rodriguez ([email protected]) wrote:
>>
>>> > This looks really wrong. We shouldn't permit worker processes to be
>>> > blocked indefinitely
On Aug 27, 2014 10:03 PM, "Dale R. Worley" wrote:
>
> > From: Thomas Suckow
> >
> > >> From: Lennart Poettering
> > >
> > >> Note that a concept of "mount at boot if it is there, otherwise
don't"
> > >> cannot work.
> > >
> > > It worked until a week or two ago. I want it back.
> > >
> > > I'm
Am 27.08.2014 um 20:25 schrieb Ivan Shapovalov:
> On Wednesday 27 August 2014 at 20:19:45, Lennart Poettering wrote:
>> On Wed, 27.08.14 20:26, Ivan Shapovalov ([email protected]) wrote:
>>
>>> This is as proposed by Thomas in review of my hibernate-resume patchset.
>>>
>>> The objective ben
On Wed, 27.08.14 09:47, HATAYAMA, Daisuke ([email protected]) wrote:
> >Sounds like the right option here... I have now added a slightly
> >different patch (1dedb74a2e1d840b531b76b01a76979f3b57456b) that does
> >this.
> >
>
> Thanks! But this could still hang in very rare case becuase the
On Wed, 27.08.14 00:39, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> mmap code crashes when attempting to map an object of zero size.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758392
> https://bugs.freedesktop.org/show_bug.cgi?id=82894
> ---
> Oops, both my analysis and fi
> From: Thomas Suckow
>
> >> From: Lennart Poettering
> >
> >> Note that a concept of "mount at boot if it is there, otherwise don't"
> >> cannot work.
> >
> > It worked until a week or two ago. I want it back.
> >
> > I'm sure you're right that in the abstract, it cannot be made to
> > work.
On Wed, 27.08.14 10:59, Andrei Borzenkov ([email protected]) wrote:
> On Wed, Aug 27, 2014 at 10:18 AM, Thomas Bächler wrote:
> >> +[Unit]
> >> +Description=Resume from hibernation using device %f
> >> +Documentation=man:[email protected](8)
> >> +DefaultDependencies=no
> >> +Bi
On Wed, 27.08.14 08:18, Thomas Bächler ([email protected]) wrote:
> > +[Unit]
> > +Description=Resume from hibernation using device %f
> > +Documentation=man:[email protected](8)
> > +DefaultDependencies=no
> > +BindsTo=%i.device
>
> What's the purpose of BindsTo= as opposed to
On Wed, 27.08.14 13:17, Ivan Shapovalov ([email protected]) wrote:
> On Wednesday 27 August 2014 at 03:16:10, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Aug 26, 2014 at 10:21:59PM +0200, Lennart Poettering wrote:
> > > On Wed, 27.08.14 00:17, Ivan Shapovalov ([email protected]) wrote:
On Wed, 27.08.14 10:19, Umut Tezduyar Lindskog ([email protected]) wrote:
>
> Hi Ivan,
>
> Great job!
>
> I was wondering if a ./configure switch makes sense to disable it.
> Embedded devices won't be using it.
Sure! I'd be happy to merge a patch that makes this compile-time optional.
Lennart
On Wed, 27.08.14 04:45, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> > +}
> > +
> > +bcon = context_new(mycon);
> > +if (!bcon)
> > +goto out;
> This will return 0. Should return log_oom() or ENOMEM instead?
Please use ENOMEM here, don't use log
On Wednesday 27 August 2014 at 20:19:45, Lennart Poettering wrote:
> On Wed, 27.08.14 20:26, Ivan Shapovalov ([email protected]) wrote:
>
> > This is as proposed by Thomas in review of my hibernate-resume patchset.
> >
> > The objective benefit of this change is that in_initrd() function
On Wed, 27.08.14 20:26, Ivan Shapovalov ([email protected]) wrote:
> This is as proposed by Thomas in review of my hibernate-resume patchset.
>
> The objective benefit of this change is that in_initrd() function is used
> for checking, which not only checks for /etc/initrd-release, but also ve
They were left from an early review iteration, when hibernate-resume
functionality was intended to work also outside of initramfs.
Now this is not the case, and these dependencies became redundant
as systemd-fsck-root.service can never be part of initramfs, and
systemd-remount-fs.service makes litt
---
units/initrd-cleanup.service.in| 2 +-
units/initrd-fs.target | 2 +-
units/initrd-parse-etc.service.in | 2 +-
units/initrd-root-fs.target| 2 +-
units/initrd-switch-root.service.in| 2 +-
units/initrd-switch-root.target
This is as proposed by Thomas in review of my hibernate-resume patchset.
The objective benefit of this change is that in_initrd() function is used
for checking, which not only checks for /etc/initrd-release, but also verifies
that the rootfs is on a virtual device.
Ivan Shapovalov (2):
units: a
---
man/systemd.unit.xml | 13 +
src/core/condition.c | 17 +
src/core/load-fragment-gperf.gperf.m4 | 1 +
src/shared/condition-util.c | 1 +
src/shared/condition-util.h | 1 +
5 files changed, 33 insertions(+)
d
Hi Miroslav,
>> ConnMan is a single daemon solution doing NTP, DHCP and DNS all in
>> one place. Any sort of callouts are costing time. And that is time
>> that has a visible user impact. There is nothing that justifies to
>> have a bit more nanosecond accuracy of synchronized time than making
>>
On 08/27/2014 03:49 AM, Lennart Poettering wrote:
> On Tue, 26.08.14 18:11, Mantas Mikulėnas ([email protected]) wrote:
>
>> On Tue, Aug 26, 2014 at 5:07 PM, WaLyong Cho wrote:
>>>
>>> This case really shouldn't be happen. (But actually sometime that was
>>> happen.) Eeven if happened we maybe wa
The kernel timestamp (recv_time) is made earlier than current time
(now_ts), use the timestamp captured before sending packet directly.
---
src/timesync/timesyncd-manager.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesy
---
src/timesync/timesyncd-manager.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index 3339606..2b0580c 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@
When I was looking at the timesyncd code I noticed few issues that I
thought could be easily fixed and you might be interested in.
The last two patches is an attempt to fix the problem with frequent
polling. I'm not sure if this is robust enough, I feel like a minor
change in the code could break
When all servers are exhausted, wait for one poll interval before trying
to connect again to the first server in the list. Also, keep increasing
the polling interval to make sure a client not getting any valid replies
will not send requests to any server more frequently than is allowed by
the maxim
NTPv4 servers don't reply with unsynchronized status when they lost
synchronization, they only keep increasing the root dispersion and it's
up to the client to decide at which point they no longer consider it
synchronized.
Ignore replies with root distance over 5 seconds.
---
src/timesync/timesyn
The shortest time constant that is stable with the kernel PLL (compiled
with SHIFT_PLL=2) is about log2 of update interval - 3. Set the constant
to poll - 2 to make room for one missed update.
---
src/timesync/timesyncd-manager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
After receiving a reply from the server, allow two missed replies before
switching to another server to avoid unnecessary clock hopping when
packets are getting lost in the network.
---
src/timesync/timesyncd-manager.c | 27 ++-
src/timesync/timesyncd-manager.h | 1 +
2 fi
---
src/timesync/timesyncd-manager.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index d80c72f..60f39c6 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@ -574,7 +574,
---
src/timesync/timesyncd-manager.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/timesync/timesyncd-manager.c b/src/timesync/timesyncd-manager.c
index 9f12149..d1f77a8 100644
--- a/src/timesync/timesyncd-manager.c
+++ b/src/timesync/timesyncd-manager.c
@@ -735,7 +735,
I've just been pointed to this discussion from #debian-systemd, where I dropped
in to suggest that Debian packaging of systemd should probably abort
installation if incompatible config like this is detected (I ended up with a
non-booting test server, no harm done).
I thought I'd help elaborate
On Wed, Aug 27, 2014 at 06:58:17PM +1200, Chris Tillman wrote:
> Ummm, luser here, how would I know if it was BE mode? That would stand for
> big-endian? I reckon so, as I wouldn't know how to change it. /proc/cpuinfo
> didn't mention it.
Yeah, big-endian. With PowerPC it is more complicated since
If one has a config like:
d /tmp 1777 root root -
X /tmp/important_mount
All files below /tmp/important_mount will be deleted as the
/tmp/important_mount item will spuriously inherit a max age of 0
from /tmp.
/tmp has a max age of 0 but age_set is (of course) false.
Fix this by checking ->age_set
On Wed, Aug 27, 2014 at 11:18:11AM +0200, Umut Tezduyar Lindskog wrote:
> On Wed, Aug 27, 2014 at 3:24 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Tue, Aug 26, 2014 at 08:49:29PM -0400, Gary Mort wrote:
> >> Socket based activation for systemd is a really cool feature for my
> >> dev system.
>
On Wed, Aug 27, 2014 at 07:51:17AM +0100, Alastair Scobie wrote:
> Apologies if this isn't the appropriate mailing list to raise this question.
>
> Is there any way to override dependencies without resorting to
> editing files in /lib?
>
> For example, with a stock EL7.0 machine, getty.target is
On Tue, Aug 26, 2014 at 10:28:54PM +0200, Lennart Poettering wrote:
> On Tue, 26.08.14 22:11, Lukasz Stelmach ([email protected]) wrote:
>
> > Greetings.
> >
> > According to systemd.special(7) "all services where correct time is
> > essential should be ordered after" time-sync.target. Implicitly
On Wed, Aug 27, 2014 at 10:17 AM, Mads wrote:
> Is there a way to force a DHCPv4 release/renew with systemd-networkd?
We don't currently allow dynamic interaction with networkd, but you
can force renew the release by either restarting networkd or
unplugging/replugging the cable (or switching your
Lennart Poettering píše v Út 26. 08. 2014 v 20:26 +0200:
> On Tue, 26.08.14 13:36, Lukas Nykryn ([email protected]) wrote:
>
> Looks good! Please commit!
>
> > ---
> > src/shared/install.c | 7 ++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/src/shared/install.c
On Tue, Aug 26, 2014 at 09:08:47AM -0700, Marcel Holtmann wrote:
> ConnMan is a single daemon solution doing NTP, DHCP and DNS all in
> one place. Any sort of callouts are costing time. And that is time
> that has a visible user impact. There is nothing that justifies to
> have a bit more nanosecon
On Wed, Aug 27, 2014 at 3:24 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Aug 26, 2014 at 08:49:29PM -0400, Gary Mort wrote:
>> Socket based activation for systemd is a really cool feature for my
>> dev system.
>>
>> Prior to using socket based activation, on my dev system I would
>> have 2 ch
On Wednesday 27 August 2014 at 03:16:10, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Aug 26, 2014 at 10:21:59PM +0200, Lennart Poettering wrote:
> > On Wed, 27.08.14 00:17, Ivan Shapovalov ([email protected]) wrote:
> > > This patchset allows systemd to parse resume= kernel command line
>
On Tue, 2014-08-26 at 14:00 +0200, Lennart Poettering wrote:
> On Tue, 26.08.14 12:17, Tanu Kaskinen ([email protected]) wrote:
>
> > Hi,
> >
> > If I want to designate some sound card to be shared between seats,
> > then I suppose that sound card shouldn't be assigned to any seats.
>
Hallo
During a task of migration of multiple servers to a systemd-based
distribution I was wondering if there would be a way of setting the
retentiontime of journald per unit.
In some cases e.g. there are limits for special program e.g. webserver
where it is not allowed to keep the logs as long a
Hi!
Is there a way to force a DHCPv4 release/renew with systemd-networkd?
- Mads
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 08/27/2014 04:54 AM, Lennart Poettering wrote:
> On Tue, 26.08.14 21:52, Lennart Poettering ([email protected]) wrote:
>
>>
>> On Thu, 21.08.14 12:58, WaLyong Cho ([email protected]) wrote:
>>
>>> If selinux is disabled and smack is only enabled, smack label is
>>> relable-ed by labe
Hi Ivan,
Great job!
I was wondering if a ./configure switch makes sense to disable it.
Embedded devices won't be using it.
Thanks
On Sat, Aug 23, 2014 at 2:47 PM, Ivan Shapovalov wrote:
> This patchset allows systemd to parse resume= kernel command line parameter
> and initiate resume from the
On 26.08.2014 22:28, Lennart Poettering wrote:
> On Tue, 26.08.14 22:11, Lukasz Stelmach ([email protected]) wrote:
>
>> Greetings.
>>
>> According to systemd.special(7) "all services where correct time is
>> essential should be ordered after" time-sync.target. Implicitly this
>> means that if syst
Am 27.08.2014 um 09:22 schrieb Ivan Shapovalov:
>>> +[Unit]
>>> +Description=Resume from hibernation using device %f
>>> +Documentation=man:[email protected](8)
>>> +DefaultDependencies=no
>>> +BindsTo=%i.device
>>
>> What's the purpose of BindsTo= as opposed to Requires= here. They
Apologies if this isn't the appropriate mailing list to raise this question.
Is there any way to override dependencies without resorting to editing
files in /lib?
For example, with a stock EL7.0 machine, getty.target is "wanted" by
multi-user.target through configuration in /lib/systemd. I'd
On Wednesday 27 August 2014 at 08:18:38, Thomas Bächler wrote:
> Am 26.08.2014 um 22:17 schrieb Ivan Shapovalov:
> > This can be used to initiate a resume from hibernation by path to a swap
> > device containing the hibernation image.
> >
> > The respective templated unit is also added. It is in
53 matches
Mail list logo
