search for: wintertim

When the Central European Time was last switched back to standard, at 03:00 last Sunday, the October 30th, a process died on one of my Windows clients with a mysterious "unknown error". When it was restarted it just went merrily on with its task. Luckily it wasn't part of a life support system. I found out that the immediate cause was how file timestamps were interpreted/presented

...urope), and use daylight saving time (aka DST aka summertime). I upgraded my Samba server from 3.0.20b to 3.0.21c. Got complaints from a user that all his *WINTER* files modification date mysteriously shifted one hour ahead. It took me some time to find out the culprit, since we just switched from wintertime to summertime. On Unix (tested both Solaris 9 and RedHate Enterprise 4), created two files using touch (with the -t flag): - winter, timestamp set to 2 Mar 06 9:00 - summer, timestamp set to 2 Apr 06 9:00 Using Samba 3.0.20b my WinPC (XP Pro) with time set in summertime (today) shows: - wint...

Hi, I have a time series of 38 wintertime average snow depths measured at a particular meteorological station. The data appear to undergo a "climate shift" in the early 1980s: before the shift the mean and sd are 152 +/- 58, after the shift 92 +/- 36. The distribution is not normal; there's a hard limit at zero of course...

eyesight kazoo sumner boletus blair audubon privilege egyptian cavalcade wintertime monocotyledon legion planetarium ago bowstring superfluity behold academia cellulose

Hi list, I am a bit confused how the time sync between samba and windows should be done correctly. On the samba server I have set the CMOS time to GMT (UTC) and my timezone is UTC+2 (germany). On windows the CMOS time is set to my timezone (windows can't handle UTC, did that change? XP here, but dualboot to linux) and as I issue net time \\server /set /YES it sets the time but minus one

...oks and calendars are possible too this way ( and at last anonymous read only ones ). All other servers i know use some db backend. I guess you will have hard times with clients, cause there are all kind of known bugs. Specially serial appointment with/and different timezones over summertime and wintertime changes seems difficult to code. Best way all in UTC and let the client convert it in its local timezone. Also there are two ways of invitations notices via mail , let the client send it, or the server has to do it ( or perhaps combinate ). So resources calenders are needed too ,for auto booking...

I've been once in a while over the years thinking about implementing CalDAV (and CardDAV) to Dovecot. It might be time to start that soon. Does anyone have any suggestions? So far my main goals would be: - scalable, of course - configurable storage (object storage, regular fs, maybe some key-value dbs, maybe storing as emails) - efficient indexes (potentially using key-value dbs? or maybe