Achim Gratz wrote:
Thanks, I think it'll come in handy once I know what program actually tries to deep-dive on the disk.
I thought you said it was when the ntp start up script ran? and that you tried both with and without the "chroot" with same result. With that, the only thing the startup script should be doing is running the ntp daemon. I.e. here's the systemV init code: case "$1" in start) #<linda>## so pretend this is set to "no", initially (il if [ "$NTPD_FORCE_SYNC_ON_STARTUP" = "yes" ]; then # get the initial date from the timeservers configured in ntp.conf ntpd_is_running || $0 ntptimeset fi echo -n "Starting network time protocol daemon (NTPD)" # do we need a refclock symlink? parse_symlink #<linda># this is for the chroot case # do we run chrooted? test "${NTPD_RUN_CHROOTED}" = "yes" && prepare_chroot #<linda>#just break this line down for your test startproc $NTPD_BIN -p ${NTPD_PID#${CHROOT_PREFIX}} $NTPD_OPTIONS -c $NTP_CONF if [ -n "${NTP_KEYS}" ]; then runtime_configuration #<linda> ignore this for 1 test.. fi rc_status -v ---------- That's the startup case. -- just use the values after NTPD_BIN..like NTPD_BIN="/usr/sbin/ntpd" NTPD_OPTIONS="-g -u ntp:ntp" If that is a the area of your problem, add "-d" to NTPD_OPTIONS /usr/sbin/ntpd -g -u ntp:ntp -n [-q] [-A] Use -q to have it exit after the first time set - that would be a minimal case, I would think. Maybe -A to have it run w/o auth calls (if they would be the problem). -------------- This type of script is what is missing in "systemd" -- that makes it hard to debug problems like these, BTW, so going back to an earlier suse version to pull out the start scripts is a good start-point for seeing what systemd "should" be doing. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org