Way OT: Re. lines of code [was Re: implicit linkage]

2014-10-13 Thread Miles Fidelman
Chris Bannister wrote: On Mon, Oct 13, 2014 at 07:14:29PM +0900, Joel Rees wrote: On Mon, Oct 13, 2014 at 4:18 PM, Jonathan Dowland j...@debian.org wrote: On Sun, Oct 12, 2014 at 02:48:55PM -0400, Steve Litt wrote: On Sun, 12 Oct 2014 19:02:08 +0100 Martin Read zen75...@zen.co.uk wrote: On

Re: Way OT: Re. lines of code [was Re: implicit linkage]

2014-10-13 Thread Joel Rees
On Mon, Oct 13, 2014 at 10:47 PM, Miles Fidelman mfidel...@meetinghouse.net wrote: Chris Bannister wrote: On Mon, Oct 13, 2014 at 07:14:29PM +0900, Joel Rees wrote: On Mon, Oct 13, 2014 at 4:18 PM, Jonathan Dowland j...@debian.org wrote: On Sun, Oct 12, 2014 at 02:48:55PM -0400, Steve Litt

Re: Way OT: Re. lines of code [was Re: implicit linkage]

2014-10-13 Thread Steve Litt
On Tue, 14 Oct 2014 07:37:17 +0900 Joel Rees joel.r...@gmail.com wrote: The only way to fix that in systemd is for systemd to delegate the complicated stuff like managing dbus to child processes, so the processes that will occasionally stall won't impact the whole system as much. When/if

Re: Way OT: Re. lines of code [was Re: implicit linkage]

2014-10-13 Thread Ansgar Burchardt
Joel Rees joel.r...@gmail.com writes: If pid 1 gets stalled, lots of things all over the system get to wait for something important that can't happen until pid 1 gets un-stalled, and that's true even with quad core. It may not freeze every process, but it can cause dropped packets and such