New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Comments
Click the link and then refresh browser fixes that.
Yeah, but last time I checked, they don't hash passwords. There's no excuse for that... EVER.
I would say abuse and support
If you're the MarkC I think you are, abuse is the -last- thing you get to complain about.
We have an invoice coming up due this week... looks like we'll be looking for an alternative now.
No, a provider set wrong timezone in host, even if guest set right timezone but the hours still goes wrong.
Just like they are late in interview appointment. They just not keep time. After that I will check the guest time on every host reboot I've notice.
So what's a "right" timezone for the host? The timezone the server is located in? THe timezone the hoster is located in? The timezone you are located in?
You either are explaining yourself incorrectly or you do not understand. The timezone is user dependent. The actual time is the providers responsibly, but the timezone is yours.
I guess they did wrong timezone and actual time matching.
Let say now is 2am in GMT.
The right GMT+8 time will be 10am
If provider set timezone as GMT+7 but the setup guy locate in GMT+6 zone.
The time of the guy is 8am but s/he set wrong and (not sync with ntp).
Then GMT+8 time in guest will become 9am.
For time, yes, not tiemzone.
Symlink the correct zone to /etc/localtime
I did that but the hours get may be 10 hours difference, so I guest the provider set timezone incorrect.
Or... the provider set right timezone but the time set 10 hours wrong.
The time has to be setup on the hostnode. But timezone has to be set per container. Example, run ln -sf ../usr/share/zoneinfo/America/Chicago /etc/localtime for central time
I would put my money on this one
I would say set incorrect timezone is mistake, but set time 10 hours difference is shit.
Finally I had quit all provider have bad time keeping, they just don't know what is a server.
It really does look more like you do not understand this function fully, on OpenVZ, the timezone of the host node makes no difference to you the user, as long as unixtime is set correct. You as a user have 100% control over the timezone, 0% control over unixtime
That's what you think, son.
Francisco
I prefer the nodes to be UTC, that way you don't have to mess with daylight savings.
Openstatus is a pita to setup, and Pingdom has been reliable enough in my opinion.
http://up.tomoyo.eu/
The reports mentioned there are pretty accurate seeing as it's monitoring my home connection, and at the reported times, I indeed did not have internet.
This is not something that I "worry" about, but related to not having the time set correctly, a pet peeve of mine is not having a locale set, so the first time you apt-get or anything you get a ton of error messages thrown at you. Just set all templates to en_US.UTF-8 or some sane default. Yes, some customers will have to reconfigure it, but everyone has to reconfigure it already the way it is + deal with the annoying error messages.
Really? O_o It's been easy as hell for me. Setup a master, then make a template of the config. Setup a client, template the config. Future setups of either then take ~3 mins.