but, when i do that i get “Error: Can not update the dynamic
configuration policy.” and every time i go back to that YaST dialog i
see it has reverted to not running the daemon, see: http://susepaste.org/48252341
strange! i have tried disabling Novell’s App Armor and run chrooted or
not, with no change
On 09/08/2012 08:35 PM, Martin Helm wrote:
> Am 08.09.2012 20:13, schrieb dd@home.dk:
>> idiot!
> Hi dd, now you have to ban yourself, because you insulted yourself
i couldn’t ban anyone, even if i wanted to.
anyway, today i boot and see that what i did yesterday didn’t ‘fix’ the
problem, it only provided a short term work around to eliminate the
symptoms for ONE session…
what is happening: because i have edited resolv.conf (to include
google’s 8.8.8.8 etc) there is a conflict between it and
resolv.conf.netconfig which is blocking the system from running ntpd…
sigh!
so, i guess i have to either let the startup scripts do as they wish
with resolv.conf, OR figure out how to do 8.8.8.8 the ‘correct’ way, OR
not use 8.8.8.8, OR continue to live without ntpd running, locally…
double sigh!
now, i will ban myself for a few hours (while i drive cross country)…
