On Fri, Oct 10, 2014 at 11:54 PM, Anatol Pomozov
wrote:
> 1) Why not to make the timeout configurable through config file? There
> is already udev.conf you can put config option there. Thus people with
> modprobe issues can easily "fix" the problem. And then decrease
> default timeout back to 30 s
Hi
On Fri, Sep 12, 2014 at 1:09 PM, Luis R. Rodriguez
wrote:
> On Thu, Sep 11, 2014 at 10:48 PM, Tom Gundersen wrote:
>> On Fri, Sep 12, 2014 at 12:26 AM, Luis R. Rodriguez
>> wrote:
>>> On Thu, Sep 11, 2014 at 2:43 PM, Tom Gundersen wrote:
How about simply introducing a new flag to finit
On 10/10/2014 04:42 PM, Lukasz Skalski wrote:
> 'ListQueuedOwners' method should return 'NameHasNoOwner' error
> if chosen name is not available on bus.
Applied, thanks!
>
> ---
> src/bus-proxyd/bus-proxyd.c | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/src/bus-proxyd/bus-p
> From: Tom Gundersen
> What we do, however, is to expose the configuration state using the
> sd-network C API, which external programs can watch and react on (see
> how timesyncd and resolved currently works).
In a situation where one wants to do what a "hook" does, having a
separate daemon pro
В Fri, 10 Oct 2014 10:14:47 -0700
PGNd пишет:
> systemd v214 introduced the new network-related target, "network-pre.target".
>
> It cleanly provides a convenient and timley pre-network state trigger for
> Before= use in unit ordering.
>
> As originally conceived, and currently implemented, it
On Fri, Oct 10, 2014 at 7:14 PM, PGNd wrote:
> (2) [systemd-networkd] does not appear to be required for either
> network.target, or network-online.target ...
Correct.
The point of network-pre.target is that whatever network manager you
are using must be ordered After= it, so that your firewall
systemd v214 introduced the new network-related target, "network-pre.target".
It cleanly provides a convenient and timley pre-network state trigger for
Before= use in unit ordering.
As originally conceived, and currently implemented, it's of particular use for
secure, early init of firewalls,
Ping?
I will submit a patch that fixes this regression for SCSI, but I suspect
other transports will have problems, too, since the by-path links will
now be missing.
On 10/07/2014, I wrote:
> Date: Tue, 07 Oct 2014 21:21:11 +0500
> From: Lee Duncan
> To: systemd-devel@lists.freedesktop.org
> Su
Lennart,
Am 10.10.2014 um 18:44 schrieb Lennart Poettering:
> It's a bit more complex. While UML, qemu, kvm, currently don't, LXC,
> systemd-nspawn and libvirt-lxc all do talk directly to machined. (Note
> that LXC and libvirt-lxc are separate codebases, the latter is *not* a
> wrapper around the
On Wed, 17.09.14 10:24, Richard Weinberger (richard.weinber...@gmail.com) wrote:
> On Wed, Sep 17, 2014 at 1:09 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > On Tue, Sep 16, 2014 at 05:31:05PM +0200, Thomas Meyer wrote:
> >> Hi,
> >>
> >> I wrote a small patch for user-mode linux to register with
On Tue, 16.09.14 17:31, Thomas Meyer (tho...@m3y3r.de) wrote:
Heya,
> I wrote a small patch for user-mode linux to register with machined by
> calling "CreateMachine". Is this a good idea to do so?
Well, this depends, how UML positions itself. If it's just a tool that
other management software s
'ListQueuedOwners' method should return 'NameHasNoOwner' error
if chosen name is not available on bus.
---
src/bus-proxyd/bus-proxyd.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/src/bus-proxyd/bus-proxyd.c b/src/bus-proxyd/bus-proxyd.c
index 4f44825..52498f3 100644
--- a/src/bus
On Thu, Oct 09, 2014 at 07:24:07AM +0200, Marcel Holtmann wrote:
> For the wpa_supplicant, we are going to fix that one with a proper daemon
> soon.
Interesting. Can you shed some light on this?
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists
Thanks to everybody for taking the time to review this (and to explain
git over email to me!).
I know all of you -- and especially Lennart -- are pressed for time
with that LibreOffice merge:-)
Best Regards,
Tobias
On Fri, Oct 10, 2014 at 12:57 PM, Lennart Poettering
wrote:
> On Thu, 09.10.14 2
On Wed, 17.09.14 12:44, Günther J. Niederwimmer (g...@gjn.priv.at) wrote:
> Hello,
>
> I have a problem with kinit (krb5)
> before on my old system this works with a cron file
>
> @reboot root /usr/bin/sleep 120 && /usr/bin/kinit -k host/.
>
> now with systemd I can't say why, the e
On Thu, 18.09.14 21:21, Emil Renner Berthing (syst...@esmil.dk) wrote:
> Hi Tom,
>
> On 18 September 2014 18:29, Tom Gundersen wrote:
> > In general, I don't think we should add patches for the sole purpose
> > of non-glibc compatibility. You would in most cases be much better
> > served by addi
---
src/journal/journalctl.c | 133 +--
1 file changed, 58 insertions(+), 75 deletions(-)
diff --git a/src/journal/journalctl.c b/src/journal/journalctl.c
index 328e40b..550b610 100644
--- a/src/journal/journalctl.c
+++ b/src/journal/journalctl.c
@@ -82
On Thu, 18.09.14 15:24, Emil Renner Berthing (syst...@esmil.dk) wrote:
What's the rationale here? The GNU version of basename() appears a lot
more useful than the POSIX. I am find with switching to the POSIX
version of libc calls if both have more or less equivalent
functionality or they are used
On Thu, 18.09.14 15:24, Emil Renner Berthing (syst...@esmil.dk) wrote:
> This is also the only place where FTW_ACTIONRETVAL is used, so
> this makes systemd compile without SELinux or SMACK support
> when the standard library doesn't support this extension.
I applied this one. It's probably a goo
On 10/10/2014 12:29 PM, Lukasz Skalski wrote:
> Commit 710fc9779b7c (kdbus repo) introduced attaching items[]
> instead of name[] in kdbus_cmd_conn_info struct. Commit 581fe6c81
> (systemd repo) caught up with this change, but item size was not
> properly calculated.
Thanks for spotting this!
App
Commit 710fc9779b7c (kdbus repo) introduced attaching items[]
instead of name[] in kdbus_cmd_conn_info struct. Commit 581fe6c81
(systemd repo) caught up with this change, but item size was not
properly calculated.
---
src/libsystemd/sd-bus/bus-control.c | 11 +--
1 file changed, 5 inserti
On Fri, 10.10.14 01:35, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> On Thu, Oct 09, 2014 at 01:41:24AM +0200, Lennart Poettering wrote:
> > The ExecStart=/bin/true we just add because current systemd versions
> > refuse to run service units that have no ExecStart= set. It is on the
>
On Thu, 09.10.14 20:28, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
>
> On 10/09/2014 02:26 PM, Lennart Poettering wrote:
> >On Thu, 09.10.14 12:14, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
> >
> >>On 10/08/2014 11:41 PM, Lennart Poettering wrote:
> >>>TODO list to allow services a
On Thu, 09.10.14 23:53, James Lott (ja...@lottspot.com) wrote:
> I am using a setup which retains the CAP_NET_ADMIN capability inside the
> container and allows openvpn to setup the device. No persistent devices are
> involved. Below, I have included a snippet from a shell session which shows
>
On Fri, 10.10.14 05:57, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> On Thu, Oct 09, 2014 at 07:01:11PM +0530, Susant Sahani wrote:
> > CID 1237543 (#1 of 1): Unchecked return value from library
> > (CHECKED_RETURN)
> > ---
> > src/socket-proxy/socket-proxyd.c | 2 +-
> > 1 file chang
On 10/09/2014 11:35 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Oct 09, 2014 at 01:41:24AM +0200, Lennart Poettering wrote:
The ExecStart=/bin/true we just add because current systemd versions
refuse to run service units that have no ExecStart= set. It is on the
TODO list to allow services a
26 matches
Mail list logo
