On 11/25/2014 12:05 PM, Steve Dickson wrote:
From: Tom Gundersen t...@jklm.no
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that
Hello,
On 11/22/2014 09:24 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Fri, Nov 21, 2014 at 11:43:47AM -0500, Steve Dickson wrote:
From: Tom Gundersen t...@jklm.no
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now
From: Tom Gundersen t...@jklm.no
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that we no longer need to worry about any
ordering
On Fri, Nov 21, 2014 at 11:43:47AM -0500, Steve Dickson wrote:
From: Tom Gundersen t...@jklm.no
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot.
Hi-
On Feb 1, 2012, at 11:37 AM, Tom Gundersen wrote:
Hi Chuck,
Thanks for the feedback.
On Wed, Feb 1, 2012 at 4:32 PM, Chuck Lever chuck.le...@oracle.com wrote:
Typically this is done by breaking the proposed change into smaller atomic
patches. Is that not possible in this case?
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that we no longer need to worry about any
ordering dependencies.
This is based on a patch
Hi,
exactly what version of rpcbind is this supposed to be applied against?
(Even better, could you post a link to a git repo?)
Confused,
Zbyszek
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Hi Zbyszek,
2012/2/1 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
exactly what version of rpcbind is this supposed to be applied against?
Current git head.
(Even better, could you post a link to a git repo?)
Sure, the patch can be found on my wip branch here:
Adding libtirpc developers mailing list...
On Feb 1, 2012, at 6:47 AM, Tom Gundersen wrote:
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This
Hi Chuck,
Thanks for the feedback.
On Wed, Feb 1, 2012 at 4:32 PM, Chuck Lever chuck.le...@oracle.com wrote:
Typically this is done by breaking the proposed change into smaller atomic
patches. Is that not possible in this case?
Not entirely sure what you have in mind, I don't immediately
On Feb 1, 2012, at 11:37 AM, Tom Gundersen wrote:
Hi Chuck,
Thanks for the feedback.
On Wed, Feb 1, 2012 at 4:32 PM, Chuck Lever chuck.le...@oracle.com wrote:
Typically this is done by breaking the proposed change into smaller atomic
patches. Is that not possible in this case?
Not
On Wed, Feb 1, 2012 at 7:16 PM, Chuck Lever chuck.le...@oracle.com wrote:
Submit the patch you have below, then white space fixes become subsequent
clean up patches. Not only is review easier now, but if we come back to
these changes in a year to fix bugs, it's easier for us to re-learn what
Hi-
On Feb 1, 2012, at 6:47 AM, Tom Gundersen wrote:
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that we no longer need to worry
On Wed, 01.02.12 17:37, Tom Gundersen (t...@jklm.no) wrote:
+ /* Try to find if one of the systemd sockets we were given match
+ * our netconfig structure. */
+
+ for (fd = SD_LISTEN_FDS_START; fd SD_LISTEN_FDS_START + n; fd++) {
+ struct __rpc_sockinfo
On Feb 1, 2012, at 4:45 PM, Lennart Poettering wrote:
On Wed, 01.02.12 17:37, Tom Gundersen (t...@jklm.no) wrote:
+ /* Try to find if one of the systemd sockets we were given match
+ * our netconfig structure. */
+
+ for (fd = SD_LISTEN_FDS_START; fd SD_LISTEN_FDS_START + n;
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that we no longer need to worry about any
ordering dependencies.
This is based on a patch
On 22/12/11 22:05, Tom Gundersen wrote:
Making rpcbind sockect activated will greatly simplify
its integration in systemd systems. In essence, other services
may now assume that rpcbind is always available, even during very
early boot. This means that we no longer need to worry about any
17 matches
Mail list logo
