I don't know where to report it, I even don't know if it is a bug or not. But I'm using unraid 5 rc 11 with  SimpleFeatures v1.0.11.

 

This is a screenshot of my time configuration: https://dl.dropbox.com/u/64092960/clocksettings.jpg

 

The problem is, I've set my time in unraid to UTC+ 1. And it displays the time correctly. But it sets my bios clock to UTC.

I use my bios to wake up my server at a specific time. (7 am). So I've to set my bios wake up time to 6am, since unraid changes the time in the bios every time I boot into the os .

 

But the real problem is, that we have "Daylight saving time" in the country where I live. I think my bios will stay at UTC time. But my unraid time will change. So my server will wake one hour later. => result : parity checks and other shedules can't be executes since the server sleeps after 1 hour . Does anyboy know how I can set the clock it the bios, so it's the same as in unraid?

 

Thanks in advance

 

And if anyone could help me getting my go script executed at boot I would also be very thankful : http://lime-technology.com/forum/index.php?topic=26253.msg229501#msg229501

 

edit: when I run "clock" command from terminal, it gives back UTC time instead of UTC+1 , But crontab utilizes UTC+1 for it sheduled tasks.

 

Configure the NTP server in your router with correct DST settings and use the router NTP server for unRAID.

Hmmm ty, will try that

Think it will not help.. most probably ntp server will always return utc on router exactly like a public ntp server.

 

If I understand the thing can be most probably related to kernel behaving like system clock is set to utc and getting/setting time on it as that... may be related to UTC param on /etc/adjtime or /etc/sysconfig/clock... anyway on unRaid may be a bit complex to properly fix this as when go file runs the clock is probably already adjusted (system time already set from rtc time as if rtc time is utc...), maybe there could be an workaround changing this from go file but it would most probably need time being set incorrectly at startup and only then fixed... but maybe some linux expert can comment more on that or maybe tom could add an option for that if you ask him

okay The problem is that my go file isn't working  check my other thread.