Mailinglist Archive: opensuse (1002 mails)

[Roger Oberholtzer <roger@xxxxxx>]

On Mon, 2011-07-18 at 12:05 +0200, Per Jessen wrote:
> Roger Oberholtzer wrote:
>
> > On Mon, 2011-07-18 at 11:21 +0200, Per Jessen wrote:
> > > Roger Oberholtzer wrote:
> > >
> > > > > > IMO, the problem is ntp, not the system start stuff. Since I
> > > > > > have effectively removed my network from the system startup
> > > > > > environment, I would find it hard to see that environment being
> > > > > > able to solve ordering or dependency issues. How could a system
> > > > > > service know that some user will, via their own non-system
> > > > > > configuration, eventually, maybe start a network where an
> > > > > > interesting server lives?
> > > > >
> > > > > A daemon would just try to reach the interesting server, and when
> > > > > the error says "network not reachable" (or something similar) it
> > > > > means it's still not there.
> > > >
> > > > But how would a daemon know which network the interesting server is
> > > > on? Perhaps a moot point. It could re-try each time the network
> > > > configuration changed.
> > >
> > > It doesn't care about the network config - for arguments sake, let's
> > > assume it uses TCP.  In pseudo-code, you would issue a
> > >
> > > connect(<desired server address>);
> > >
> > > If the network is not available, the connect() does not succeed. 
> > > This is no different to you trying to access an external website when
> > > your network is down.  Slightly different for UDP, but essentially
> > > the same.
> >
> > Of course. But, at some point in the future, will ntp retry to make
> > the connection? On that point the jury is still out. 
> > You have presented evidence where it seems to. I have presented a
> > counter claim that shows up in my usage. I suspect ntp does retry the
> > connection when it does, and does not try again when it does not...
>
> To stick to the legal metaphors, I think the judge will dismiss your 
> claim as hear-say :-)  At least until you present evidence that the
> server is configured but not used ("ntpq -p" will show the peers).

I should add that when I restart ntp, I see this:

# rcntp restart
Shutting down network time protocol daemon (NTPD)                               
                                                                                
             done
19 Jul 00:48:36 sntp[6212]: Started sntp
2011-07-19 00:48:36.113523 (-0100) -7199.729726 +/- 0.001343 secs
Time synchronized with  ntp1.sth.netnod.se
Starting network time protocol daemon (NTPD)                                    
                                                                                
             done

# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*LOCAL(0)        .LOCL.          10 l    7   64    3    0.000    0.000   0.000
+ntp1.sth.netnod .PPS.            1 u    1   64    3    2.506   -0.626   1.228


> -- 
> Per Jessen, Zürich (18.5°C)

-- 
Roger Oberholtzer

OPQ Systems / Ramböll RST

Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden

Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696

SHAW'S PRINCIPAL
    Build a system that even a fool can use,
    and only a fool will want to use it.

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx