Good day all,
Quick question re ntpdate.lrp package. When monitoring from webconf
I see it is always stopped. When I hit the start button I get the
following error
Daemon Status
Running start command ...
Running ntpdate to synchronize clock.
The command failed. Usually this is due to
Hi Darcy,
On Thursday 01 December 2005 15:04, Darcy Parker (Home) wrote:
Good day all,
Quick question re ntpdate.lrp package. When monitoring from webconf
I see it is always stopped. When I hit the start button I get the
following error
Daemon Status
Running start command ...
Hi Darcy,
On Thursday 01 December 2005 15:04, Darcy Parker (Home) wrote:
Good day all,
Quick question re ntpdate.lrp package. When monitoring from webconf
I see it is always stopped. When I hit the start button I get the
following error
Daemon Status
Running start command ...
Darcy
Darcy Parker (Home) wrote:
Good day all,
..
Here is what I get when I run ntpdate from the command line.
imagerocfw# ntpdate -u timelord.uregina.ca
1 Dec 20:02:19 ntpdate[30561]: adjust time server 142.3.100.15 offset
-0.069286 sec
Which seems to work.
Am I missing something?
Hello Darcy,
I think it's because ntpdate is no daemon, but because the package
contains an init.d script (for initial starting the program) webconf
thinks it's a daemon.
The way I understand it, is that webconf checks for an init.d script and
also the output of ps to see if it's running. But
