plugout.net

I have checked the NAS time and that the cron service is started (it is) but I am not longer getting anything in the log file and my cron jobs are not doing anything.

Have rebooted the NAS as well as stopping and starting the service manually to no avail.

Are you sure ?

Dropbear sends nothing on the standard output and if no error is occured then there is no data appended in the cron log.

Check if a dropbear process is running with the custom post

Code: Select all

ps axf

I had powered down the NAS by pulling out the plug when I couldn't access anything after the upgrade. This had reset the clock.

Btw....i added NTP addresses but the webgui only allows IP addresses and not domain names, e.g no.pool.ntp.org, why is this?

hi firwareslut,

Currently the ntp client used by the firmware requires only IP address. It's not the standard daemon (for small NAS).

But we can change this by converting the domain before writing the conf file :whistle I will try to do a path...

And of course, by changing the daemon...

The NTP domain name stuff isn't essential but I have no idea if the IP addresses of the servers change often :D

Usually the ntp servers in stratum 2 or 3 don't change their public IP.

I do a patch to allow to use a domain name whereas an IP. When the ntp daemon starts, it find the current public address of the domain name.

See your pm

I had the same issue. My NAS didn't shut down by cron.
Reason: wrong NAS time.

Solution new NTP server

See here. http://www.hullen.de/helmut/filebox/DCF77/ntpsrvr.html

Thanks wd9895 for your suggestion.

But it's already done : in the next version, the firmware will use another ntp client.

In the same time, a ntp server will be available for synchronizing hosts with the NAS time.

Two others bugs are also fixed :
- if the ntp client is started whereas there is no Internet access, NAS time was never updated even if Internet access is restored.
- if no ntp server is set, there is a TZ offset after each rebooting