[arch-general] Fwd: /etc/cron.hourly/ntp isn't working.
I'm using openntpd ---------- Forwarded message ---------- From: root <daenyth@gmail.com> Date: Tue, Nov 25, 2008 at 21:01 Subject: cron: /usr/sbin/run-cron /etc/cron.hourly To: root /bin/stty: standard input: Inappropriate ioctl for device /bin/stty: standard input: Inappropriate ioctl for device :: Stopping OpenNTPD [BUSY] [DONE] /bin/stty: standard input: Inappropriate ioctl for device :: Starting OpenNTPD [BUSY] [DONE]
On Tue, 2008-11-25 at 21:03 -0500, Daenyth Blank wrote:
I'm using openntpd
---------- Forwarded message ---------- From: root <daenyth@gmail.com> Date: Tue, Nov 25, 2008 at 21:01 Subject: cron: /usr/sbin/run-cron /etc/cron.hourly To: root
/bin/stty: standard input: Inappropriate ioctl for device /bin/stty: standard input: Inappropriate ioctl for device :: Stopping OpenNTPD [BUSY] [DONE] /bin/stty: standard input: Inappropriate ioctl for device :: Starting OpenNTPD [BUSY] [DONE]
this is because the init scripts use some fancy options to set colors. This seems to be done by stty, which won't work on a fake tty like the one used by cron. I don't know why you're restarting openntpd from cron every hour though, as it's a daemon that keeps running all the time. Restarting it has no use.
2008/11/26 Jan de Groot <jan@jgc.homeip.net>:
On Tue, 2008-11-25 at 21:03 -0500, Daenyth Blank wrote:
I'm using openntpd
---------- Forwarded message ---------- From: root <daenyth@gmail.com> Date: Tue, Nov 25, 2008 at 21:01 Subject: cron: /usr/sbin/run-cron /etc/cron.hourly To: root
/bin/stty: standard input: Inappropriate ioctl for device /bin/stty: standard input: Inappropriate ioctl for device :: Stopping OpenNTPD [BUSY] [DONE] /bin/stty: standard input: Inappropriate ioctl for device :: Starting OpenNTPD [BUSY] [DONE]
this is because the init scripts use some fancy options to set colors. This seems to be done by stty, which won't work on a fake tty like the one used by cron. I don't know why you're restarting openntpd from cron every hour though, as it's a daemon that keeps running all the time. Restarting it has no use.
Maybe you want ntpdate instead of ntp. It's not daemon and it sysnchronizes clock everytime it's run.
On Wed, 2008-11-26 at 10:18 +0100, Lukáš Jirkovský wrote:
Maybe you want ntpdate instead of ntp. It's not daemon and it sysnchronizes clock everytime it's run.
Note that ntpdate will push a date/time change directly on every run, which causes clock jumps. This is something you don't want for some applications. Openntpd will change time with very small corrections that aren't noticable to applications. When starting openntpd with the -s option, it will correct time in one jump just like ntpdate, which could be useful on initial startup. After that, it will continue to correct time with small steps.
On Wed, Nov 26, 2008 at 2:03 AM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Tue, 2008-11-25 at 21:03 -0500, Daenyth Blank wrote:
I'm using openntpd
---------- Forwarded message ---------- From: root <daenyth@gmail.com> Date: Tue, Nov 25, 2008 at 21:01 Subject: cron: /usr/sbin/run-cron /etc/cron.hourly To: root
/bin/stty: standard input: Inappropriate ioctl for device /bin/stty: standard input: Inappropriate ioctl for device :: Stopping OpenNTPD [BUSY] [DONE] /bin/stty: standard input: Inappropriate ioctl for device :: Starting OpenNTPD [BUSY] [DONE]
this is because the init scripts use some fancy options to set colors. This seems to be done by stty, which won't work on a fake tty like the one used by cron. I don't know why you're restarting openntpd from cron every hour though, as it's a daemon that keeps running all the time. Restarting it has no use.
Hmm, this is still a valid bug - would someone mind sticking it in the bug tracker, so I can fix that?
Hmm, this is still a valid bug - would someone mind sticking it in the bug tracker, so I can fix that?
participants (4)
-
Aaron Griffin
-
Daenyth Blank
-
Jan de Groot
-
Lukáš Jirkovský