Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
when i type date in telnet i get
Fri Mar 13 01:40:20 UTC 2009, when locally it is Thurs Mar 12 8:40pm.
i have the time synced in the dlink GUI to ntp1.dlink.com and it shows the right time at the top of the page.
im having trouble getting my HD_a1 to copy to HD_b2 automatically. i can enter the command manually and it works, but automatic has failed every time. i tried setting the editcron.sh just ahead of the UTC time and rebooting but the time comes and goes with no transfer.
please help.
Offline
What is the difference between where you are and UTC - Universal Time Coordinated?
It is not unusual for systems to track time at UTC and then display it after adjusting based on the time zone - this may be nothing more than presentation of the data.
Offline
central time US, -6 (chicago)
im trying to schedule auto backup times and i want... something like 10pm here... but i dont know if i should enter that to editcron.sh as 10pm CST or as 4am UTC.
Offline
My cron jobs (not on the DNS but in Linux in general) are always scheduled using local time.
You can try scheduling a test cron job (e.g. print a message to a log) very quickly and see which one works.
Offline
I've have this problem on my dns-321 as well.
The built in date, /bin/date, seems to ignore the time zone and always give UTC.
Good news is that /ffp/bin/date works better. It gives the correct time accounting for the timezone.
I'm not sure if this is a bug or a feature and I'm not sure whether it's isolated to /bin/date, or more pervasive in the firmware. Has anyone else noticed this and investigated? Is this feature isolated to the date in /bin/busybox?
Duaine
Offline
i am getting the opposite on the DNS-343
/ffp/bin/date returns UTC and /bin/date returns local
root@DNS-343:~# /ffp/bin/date Wed Mar 10 04:01:02 UTC 2010 root@DNS-343:~# /bin/date Wed Mar 10 12:01:06 SGT 2010
talkingRock wrote:
I've have this problem on my dns-321 as well.
The built in date, /bin/date, seems to ignore the time zone and always give UTC.
Good news is that /ffp/bin/date works better. It gives the correct time accounting for the timezone.
I'm not sure if this is a bug or a feature and I'm not sure whether it's isolated to /bin/date, or more pervasive in the firmware. Has anyone else noticed this and investigated? Is this feature isolated to the date in /bin/busybox?
Duaine
Offline