Re: network manager dhcp ntp server issue



On Wed, 2013-01-16 at 13:58 +0100, Ralf Habacker wrote:
> Hi,
> 
> on opensuse 12.2 i found out that NetworkManager is not able to save ntp 
> servers provided by dhcp requests into 
> /var/run/netconfig/NetworkManager.netconfig, which is used by netconfig 
> to setup network configuration (see the following example)
> 
> linux-vaba:~ # netconfig update -m ntp-runtime -v
> debug: lockfile created (/var/run/netconfig.pid) for PID 27683
> debug: lockfile created
> debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
> debug: dns-resolver module skipped
> debug: dns-bind module skipped
> debug: dns-dnsmasq module skipped
> debug: nis module skipped
> debug: ntp-runtime Module called
> debug: Static Fallback
> debug: Use NetworkManager policy merged settings
> debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
> debug:      get_ntp_settings: NTP_SERVER_LIST=''
> debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
> linux-vaba:~ #
> 
> The appended patch (based on master branch) fixes this NetworkManager issue.
> 
> linux-vaba:~ # netconfig update -m ntp-runtime -v
> debug: lockfile created (/var/run/netconfig.pid) for PID 28013
> debug: lockfile created
> debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
> debug: dns-resolver module skipped
> debug: dns-bind module skipped
> debug: dns-dnsmasq module skipped
> debug: nis module skipped
> debug: ntp-runtime Module called
> debug: Static Fallback
> debug: Use NetworkManager policy merged settings
> debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
> debug:      get_ntp_settings: NTP_SERVER_LIST='192.168.1.224'
> debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
> debug: write_ntp_servers: 192.168.1.224
> debug: Installing new /var/run/ntp/servers-netconfig
> 
> I tested this patch on opensuse 12.2

So NetworkManager pushes out *every* DHCP option in the environment of
dispatcher scripts.  This should be happening both on 'dhcp4-change' and
'up' events.  This would be the preferred mechanism to push NTP server
and other random information to other tools like ntpd.  Is this not
working?

Dan



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]