On Sun, 19 Aug 2012, Marco d'Itri wrote:
> On Aug 19, Henrique de Moraes Holschuh wrote:
> > > But still, I agree that we should have a better way to signal to user
> > > space when an interface is ready. Not just for IPv6, but also more
> > We need better userspace glue, then. Because the netl
Excerpts from Salvo Tomaselli's message of 2012-08-05 15:35:09 -0700:
> Hello,
>
> since services might depend on other services at boot, they must be sorted.
>
> But after doing a "service foo start", and waiting for its termination, we
> don't know if the service has started or not, maybe the
On Aug 19, Henrique de Moraes Holschuh wrote:
> > But still, I agree that we should have a better way to signal to user
> > space when an interface is ready. Not just for IPv6, but also more
> We need better userspace glue, then. Because the netlink interface to
> the kernel network core and I
On Sat, 18 Aug 2012, Marco d'Itri wrote:
> But still, I agree that we should have a better way to signal to user
> space when an interface is ready. Not just for IPv6, but also more
We need better userspace glue, then. Because the netlink interface to
the kernel network core and IP stack has ex
On Sun, 19 Aug 2012 10:29:49 +0200, Bastian Blank
wrote:
>On Sun, Aug 19, 2012 at 09:12:00AM +0200, Marc Haber wrote:
>> On Sat, 18 Aug 2012 18:44:10 +0200, Bastian Blank
>> wrote:
>> >Not sure about radvd, but it needs more than existing interfaces?
>> It chokes when the Interface changes after
On Sun, Aug 19, 2012 at 09:12:00AM +0200, Marc Haber wrote:
> On Sat, 18 Aug 2012 18:44:10 +0200, Bastian Blank
> wrote:
> >Not sure about radvd, but it needs more than existing interfaces?
> It chokes when the Interface changes after it was started, causing
> very hard to debug connectivity outag
On Aug 19, Marc Haber wrote:
> IPv6 people say "renumbering is easy", which is only the case if SLAAC
This is between wishful thinking and an urban legend, so people who
actually know about IPv6 have not been saying this much in the last
years.
--
ciao,
Marco
signature.asc
Description: Digi
On Sun, Aug 19, 2012 at 09:12:54AM +0200, Marc Haber wrote:
> On Sat, 18 Aug 2012 22:43:15 +0200, m...@linux.it (Marco d'Itri) wrote:
> >Non-static addresses on a web server are not a major use case.
> IPv6 people say "renumbering is easy", which is only the case if SLAAC
> is used and DNS doesn't
On Sat, 18 Aug 2012 22:43:15 +0200, m...@linux.it (Marco d'Itri) wrote:
>Non-static addresses on a web server are not a major use case.
IPv6 people say "renumbering is easy", which is only the case if SLAAC
is used and DNS doesn't matter or is dynamically used.
>But still, I agree that we should
On Sat, 18 Aug 2012 18:44:10 +0200, Bastian Blank
wrote:
>On Sat, Aug 18, 2012 at 06:31:08PM +0200, Marc Haber wrote:
>> On Sat, 18 Aug 2012 13:10:34 -0300, Henrique de Moraes Holschuh
>> >Anything that uses IPv6 and cannot deal with dynamic changes on the host
>> >addresses is critically broken.
On Aug 18, Marc Haber wrote:
> >Anything that uses IPv6 and cannot deal with dynamic changes on the host
> >addresses is critically broken.
> That includes bind, radvd and apache, and, IIRC, sshd.
BIND definitely looks for new IP addresses:
options {
interface-interval N;
}
I think that radvd
On Sat, Aug 18, 2012 at 06:31:08PM +0200, Marc Haber wrote:
> On Sat, 18 Aug 2012 13:10:34 -0300, Henrique de Moraes Holschuh
> >Anything that uses IPv6 and cannot deal with dynamic changes on the host
> >addresses is critically broken.
> That includes bind, radvd and apache, and, IIRC, sshd.
bind
On Sat, 18 Aug 2012 13:10:34 -0300, Henrique de Moraes Holschuh
wrote:
>On Sat, 18 Aug 2012, Marc Haber wrote:
>> This is not always easy. For example, IPv6 isn't ready when ifup
>
>It is ready enough: it is activated on all interfaces where it should be
>activated.
>
>Anything that uses IPv6 and
On Sat, 18 Aug 2012, Marc Haber wrote:
> This is not always easy. For example, IPv6 isn't ready when ifup
It is ready enough: it is activated on all interfaces where it should be
activated.
Anything that uses IPv6 and cannot deal with dynamic changes on the host
addresses is critically broken.
-
On Sun, 5 Aug 2012 16:35:38 -0700, Steve Langasek
wrote:
>On Mon, Aug 06, 2012 at 12:35:09AM +0200, Salvo Tomaselli wrote:
>> Would it help to have the knowledge that, when the init script terminates,
>> the
>> service is running and ready instead of just running?
>
>This is already what's expec
Bernd,
am Mon, Aug 06, 2012 at 09:05:36AM +0200 hast du folgendes geschrieben:
> On 08/06/2012 01:30 AM, Ulrich Dangel wrote:
> > On 08/06/12 00:35, Salvo Tomaselli wrote:
> >> systemd offers a solution but it is a complete rewrite of init, it's not
> >> mature nor compatible,
> > systemd suppor
On 08/06/2012 01:30 AM, Ulrich Dangel wrote:
> On 08/06/12 00:35, Salvo Tomaselli wrote:
>
>> systemd offers a solution but it is a complete rewrite of init, it's not
>> mature nor compatible,
>
> systemd supports init scripts which means it is compatible. It is IMHO also
> mature
> as Distrib
On Mon, Aug 06, 2012 at 12:35:09AM +0200, Salvo Tomaselli wrote:
> since services might depend on other services at boot, they must be sorted.
> But after doing a "service foo start", and waiting for its termination, we
> don't know if the service has started or not, maybe the process was just
On 08/06/12 00:35, Salvo Tomaselli wrote:
> systemd offers a solution but it is a complete rewrite of init, it's not
> mature nor compatible,
systemd supports init scripts which means it is compatible. It is IMHO also
mature
as Distributions like OpenSuse or Fedora ship systemd per default.
>
Hello,
since services might depend on other services at boot, they must be sorted.
But after doing a "service foo start", and waiting for its termination, we
don't know if the service has started or not, maybe the process was just
created and is kept waiting by the sheduler, so when the next se
20 matches
Mail list logo
