From: <sl...@bl...> - 2005-04-26 12:29:29
|
I've just discovered that NTP is not working for some bizarre reason on my machine running Windows XP SP2. If I bring up the "Date and Time Properties" dialog, select the "Internet Time" tab, and then click on the "Update Now" button, Windows displays the message "Please wait while Windows synchronizes with pool.ntp.org" followed by "The time has been successfully synchronized with pool.ntp.org on 2005-04-26 at 13:13.". However, this claim is false, and the time remains whatever it was before. I have also tried with time.windows.com and time.nist.gov and it makes no difference. I have also tried from the command line with "net time /setsntp:pool.ntp.org", which claims to succeed, followed by "net time /set", which however claims it "Could not locate a time-server." and fails to update the time. Both "net time /set /setsntp:pool.ntp.org" and "net time /setsntp:pool.ntp.org /set" fail the same way. Can coLinux be interfering with this somehow? I am running "colinux 2.6.8.1-co-0.6.2-pre1 #1 Sat Sep 11 03:10:51 WEST 2004". Anyway, because I can't figure out how to get Windows to keep the correct time, I think I need to run NTP inside coLinux. But this raises some questions. How does coLinux get its time correct after I resume the machine from hibernation? Presumably it must ask Windows, right? Or does it ask the hardware directly? Is there some way I can get a program like ntpdate to automatically run inside coLinux every time I resume the machine from hibernation? I notice that my coLinux is running with a different time than Windows, about a minute faster. So presumably it is not getting the time from Windows on a regular basis. But it must do something special on resuming from hibernation. I would rather avoid setting my ntpd to ask for the time every 5 minutes, because this is considered abusive by the people who run pool.ntp.org. But I don't know how to avoid this unless there is some way to trigger an action inside coLinux on resuming from hibernation. -- Thanks, Joe Wells |
From: Robert K C. Jr - I. F. D. C. <bco...@in...> - 2005-04-26 14:08:20
|
Joe, NTP doesn't work the way you (or I) expected it would. In particular, it attempts to avoid drastic time changes, and by default if time from the server is off too much it won't reset at all, rather it assumes something is wrong. Otherwise, I believe NTP will avoid time changes of > 1 second for each minute by default. "net time /set" doesn't use NTP, it attempts to set the time from another windows machine (ie. a DC). I believe it uses SMB to accomplish this. Try running the following cmd script on your XP machine. The two /unregister lines are not a typo. Modify it to whatever time source you desire. The same script can be used on Windows 2000, or you can remove that portion if you don't need it. You only need to do this once on each machine, and if you have reliable time sources you'll be set: REM The next lines are for WIN XP (ignored in 2000) net stop w32time w32tm /unregister w32tm /unregister w32tm /register net time /setsntp:192.168.2.1 w32tm /monitor w32tm /resync net start w32time REM and for W2k net stop w32time w32tm -once net start w32time - Bob Coffman |
From: <sl...@bl...> - 2005-04-26 15:08:19
|
"Robert K Coffman Jr - Info From Data Corporation" <bco...@in...> writes: > Joe, > > NTP doesn't work the way you (or I) expected it would. In particular, it > attempts to avoid drastic time changes, and by default if time from the > server is off too much it won't reset at all, rather it assumes something is > wrong. I read that NTP would do nothing only when the time gap was quite large, much larger than just a minute or two. The time gap for me was a few minutes, so I presumed it should try to do something. > Otherwise, I believe NTP will avoid time changes of > 1 second for > each minute by default. This is a good point. So I shouldn't expect the time to get better instantly. (Still, the user interface on this sucks as it claims that the time is "resynchronized".) > "net time /set" doesn't use NTP, it attempts to set the time from another > windows machine (ie. a DC). I believe it uses SMB to accomplish this. Thanks, the help messages with "net help time" were extremely unclear on this point! > Try running the following cmd script on your XP machine. The two > /unregister lines are not a typo. Modify it to whatever time source you > desire. The same script can be used on Windows 2000, or you can remove that > portion if you don't need it. You only need to do this once on each > machine, and if you have reliable time sources you'll be set: > > REM The next lines are for WIN XP (ignored in 2000) > net stop w32time How do I get a list of all of the words I can put after "net stop"? The word "w32time" is not listed in the output of "net help stop". (I want to try to solve a completely separate problem by automating the restarting of "Windows Firewall / Internet Connection Sharing (ICS)", which I do by hand now whenever it gets wedged, which it frequently does after resuming from hibernation. I want to be able to do this from the coLinux side whenever coLinux detects that the DNS service is not responding.) > w32tm /unregister > w32tm /unregister > w32tm /register > net time /setsntp:192.168.2.1 > w32tm /monitor > w32tm /resync > net start w32time > REM and for W2k > net stop w32time > w32tm -once What does this do? The option "-once" is not listed in the help text output by just running "w32tm". Also, why stop and start the service again? > net start w32time > > - Bob Coffman Anyway, thanks for what looks like it will be an extremely helpful message! I'm still confused why the coLinux time is up to a minute out of sync with the Windows time. -- Joe |
From: Robert K C. Jr - I. F. D. C. <bco...@in...> - 2005-04-26 15:27:18
|
>>How do I get a list of all of the words I can put after "net stop"? >>The word "w32time" is not listed in the output of "net help stop". Great question. Here is one way. Right click My Computer - Manage - Go down to Services (Under Services and Applications) - Right click the service you are interested in - Properties - The first thing listed is "Service Name" which is what you want. I believe you can also use the quoted service name from the list, ie. "Windows Time". >>w32tm /unregister >> w32tm /unregister >> w32tm /register >> net time /setsntp:192.168.2.1 >> w32tm /monitor >> w32tm /resync >> net start w32time >> REM and for W2k >> net stop w32time >> w32tm -once >What does this do? The option "-once" is not listed in the help text >output by just running "w32tm". The last three lines are for w2k. I have this script set so I can run it on any machine and have it just "work." The help for -once says: -once do only one synchronization, then exit. It doesn't do anything on WinXP so it doesn't hurt to run it. >>Also, why stop and start the service again? Because of the w2k thing. I'm sure this could be cleaner, but it works! >Anyway, thanks for what looks like it will be an extremely helpful >message! No problem! - Bob Coffman |
From: <sl...@bl...> - 2005-04-26 16:18:31
|
"Robert K Coffman Jr - Info From Data Corporation" <bco...@in...> writes: > >>How do I get a list of all of the words I can put after "net stop"? > >>The word "w32time" is not listed in the output of "net help stop". > > Great question. Here is one way. Right click My Computer - Manage - For the other people reading this message, on my Windows XP SP2 machine the path is: press Windows key (to bring up the main menu), "Administrative Tools", "Computer Management". > Go down to Services (Under Services and Applications) - This can be reached more directly on my machine by: press Windows key, "Administrative Tools", "Services". > Right click the service you are interested in - Properties - The > first thing listed is "Service Name" which is what you want. Thank you! Thank you! Thank you! > I believe you can also use the quoted service name from the list, > ie. "Windows Time". I was a bit worried about using "Windows Firewall / Internet Connection Sharing (ICS)" due to the spaces, slashes, parentheses, etc. Also, the lack of confirmation that this was one of the allowed names for use with "net start" and "net stop" did not help. The short name "SharedAccess" is also not listed as a legal option for "net start" and "net stop". Fairly unhelpful help text. :-( > >> w32tm /unregister > >> w32tm /unregister > >> w32tm /register > >> net time /setsntp:192.168.2.1 > >> w32tm /monitor > >> w32tm /resync > >> net start w32time > >> REM and for W2k > >> net stop w32time > >> w32tm -once > > >What does this do? The option "-once" is not listed in the help text > >output by just running "w32tm". > > The last three lines are for w2k. I have this script set so I can run it on > any machine and have it just "work." The help for -once says: > > -once do only one synchronization, then exit. > > It doesn't do anything on WinXP so it doesn't hurt to run it. > > >>Also, why stop and start the service again? > > Because of the w2k thing. I'm sure this could be cleaner, but it works! So I can just do everything up to the line that reads "REM and for W2k"? -- Thanks, Joe |
From: <sl...@bl...> - 2005-04-26 16:35:56
|
"Robert K Coffman Jr - Info From Data Corporation" <bco...@in...> writes: > Try running the following cmd script on your XP machine. The two > /unregister lines are not a typo. Modify it to whatever time source you > desire. The same script can be used on Windows 2000, or you can remove that > portion if you don't need it. You only need to do this once on each > machine, and if you have reliable time sources you'll be set: > > REM The next lines are for WIN XP (ignored in 2000) > net stop w32time > w32tm /unregister > w32tm /unregister > w32tm /register > net time /setsntp:192.168.2.1 > w32tm /monitor > w32tm /resync > net start w32time Okay, I tried this, and it seems to have successfully set the time from the network. I deliberately messed up the clock, then ran this, and then the clock was correct. Hurray! Thanks! Now how do I get coLinux to notice? Do I have to run NTP on coLinux? Note that I got some strange error messages when I ran the above commands The output is just after this paragraph. Are these error messages correct? ---------------------------------------------------------------------- > C:\Documents and Settings\jbw\Desktop>net stop w32time > The Windows Time service is stopping. > The Windows Time service was stopped successfully. > > > C:\Documents and Settings\jbw\Desktop>w32tm /unregister > The following error occurred: Access is denied. (0x80070005) Huh? Why is access denied? I did this from an account with administrator privileges. > C:\Documents and Settings\jbw\Desktop>w32tm /unregister > W32Time successfully registered. "registered"? Huh? This should be "unregistered", right? > C:\Documents and Settings\jbw\Desktop>w32tm /register > W32Time successfully registered. > > C:\Documents and Settings\jbw\Desktop>net time /setsntp:pool.ntp.org > The command completed successfully. > > > C:\Documents and Settings\jbw\Desktop>w32tm /monitor > GetDcList failed with error code: 0x80070057. > Exiting with error 0x80070057 Huh? > C:\Documents and Settings\jbw\Desktop>w32tm /resync > Sending resync command to local computer... > The following error occurred: The RPC server is unavailable. (0x800706BA) Huh? What is with this error? > C:\Documents and Settings\jbw\Desktop>net start w32time > The Windows Time service is starting. > The Windows Time service was started successfully. ---------------------------------------------------------------------- -- Thanks, Joe |
From: Robert K C. Jr - I. F. D. C. <bco...@in...> - 2005-04-26 18:38:32
|
>Note that I got some strange error messages when I ran the above commands The output is just after this paragraph. Are these error messages correct? > C:\Documents and Settings\jbw\Desktop>w32tm /unregister > The following error occurred: Access is denied. (0x80070005) >Huh? Why is access denied? I did this from an account with administrator privileges. I'm not sure, but when I found this script it also made a note that having that line twice was necessary. It is supposed to remove the service, but for whatever reason, has to be run twice to work. > C:\Documents and Settings\jbw\Desktop>w32tm /unregister > W32Time successfully registered. >"registered"? Huh? This should be "unregistered", right? Ask Microsoft! It says the same thing here. > C:\Documents and Settings\jbw\Desktop>w32tm /register > W32Time successfully registered. > > C:\Documents and Settings\jbw\Desktop>net time /setsntp:pool.ntp.org > The command completed successfully. > > > C:\Documents and Settings\jbw\Desktop>w32tm /monitor > GetDcList failed with error code: 0x80070057. > Exiting with error 0x80070057 >Huh? /monitor will, I believe, pull time from a domain (or with alternate switches, a computer) similar to net time /set, except using NTP rather than SMB. It appears to me that your WinXP machine is not in a domain. On my machine, this finds my DCs and notes which ones have NTP server running. > C:\Documents and Settings\jbw\Desktop>w32tm /resync > Sending resync command to local computer... > The following error occurred: The RPC server is unavailable. (0x800706BA) >Huh? What is with this error? I just tried it here and mine fails also. I believe this line should actually be put after the "net start w32time" line because it requires that service to be running. I'm fixing my script.... >So I can just do everything up to the line that reads "REM and for W2k"? Yes, but change the script to put the resync after restarting w32time. - Bob |
From: <sl...@bl...> - 2005-04-26 19:12:25
|
"Robert K Coffman Jr - Info From Data Corporation" <bco...@in...> writes: > > > C:\Documents and Settings\jbw\Desktop>w32tm /monitor > > > GetDcList failed with error code: 0x80070057. > > > Exiting with error 0x80070057 > > > >Huh? > > /monitor will, I believe, pull time from a domain (or with alternate > switches, a computer) similar to net time /set, except using NTP rather than > SMB. It appears to me that your WinXP machine is not in a domain. On my > machine, this finds my DCs and notes which ones have NTP server running. Right, I am on my own, not in any domain. Does this mean this command is not actually helping me? If so, which command is succeeding in updating the time? > > > C:\Documents and Settings\jbw\Desktop>w32tm /resync > > > Sending resync command to local computer... > > > The following error occurred: The RPC server is unavailable. (0x800706BA) > > > >Huh? What is with this error? > > I just tried it here and mine fails also. I believe this line should > actually be put after the "net start w32time" line because it requires that > service to be running. I'm fixing my script.... Okay. That seems to mean this command is also not needed for me, because it can't be working, right? So that means these lines should be enough: net stop w32time w32tm /unregister w32tm /unregister w32tm /register net time /setsntp:pool.ntp.org net start w32time I'm going to go try this now. Okay, I am now looking at the results. Removing those two lines prevents the time from being fixed. Removing the "w32tm /monitor" line but keeping the "w32tm /resync" line succeeds in getting the time fixed, despite emitting the error message. Moving the "w32tm /resync" line after the "net start w32time" line succeeds in fixing the time, without the error message. Now I am trying just the "w32tm /resync" line on its own. Yes, it succeeds! Only this one line is needed: w32tm /resync All the other lines are unneeded for my problem. My big question is why the "Update Now" button in the Windows user interface is not doing this. -- Joe |
From: Sam M. <pa...@gm...> - 2005-04-26 21:37:44
|
In regards to coLinux getting the time from Windows, it only does this when booting when it mentions "Setting system clock from hardware clock" or similar. This is when coLinux checks Windows. After this point, it keeps its own time (which accounts for why there can be a discrepency). It appears to me that the problem exists in Windows, not coLinux, although it may be a result of coLinux. Sam On 26 Apr 2005 20:11:21 +0100, Joe Wells (reverse mailbox letters only for non-public replies) <sl...@bl...> wrote: > "Robert K Coffman Jr - Info From Data Corporation" <bcoffman@infofromdata= .com> writes: >=20 > > > > C:\Documents and Settings\jbw\Desktop>w32tm /monitor > > > > GetDcList failed with error code: 0x80070057. > > > > Exiting with error 0x80070057 > > > > > >Huh? > > > > /monitor will, I believe, pull time from a domain (or with alternate > > switches, a computer) similar to net time /set, except using NTP rather= than > > SMB. It appears to me that your WinXP machine is not in a domain. On = my > > machine, this finds my DCs and notes which ones have NTP server running= . >=20 > Right, I am on my own, not in any domain. >=20 > Does this mean this command is not actually helping me? If so, which > command is succeeding in updating the time? >=20 > > > > C:\Documents and Settings\jbw\Desktop>w32tm /resync > > > > Sending resync command to local computer... > > > > The following error occurred: The RPC server is unavailable. (0x800= 706BA) > > > > > >Huh? What is with this error? > > > > I just tried it here and mine fails also. I believe this line should > > actually be put after the "net start w32time" line because it requires = that > > service to be running. I'm fixing my script.... >=20 > Okay. >=20 > That seems to mean this command is also not needed for me, > because it can't be working, right? >=20 > So that means these lines should be enough: >=20 > net stop w32time > w32tm /unregister > w32tm /unregister > w32tm /register > net time /setsntp:pool.ntp.org > net start w32time >=20 > I'm going to go try this now. Okay, I am now looking at the results. > Removing those two lines prevents the time from being fixed. Removing > the "w32tm /monitor" line but keeping the "w32tm /resync" line > succeeds in getting the time fixed, despite emitting the error > message. Moving the "w32tm /resync" line after the "net start > w32time" line succeeds in fixing the time, without the error message. >=20 > Now I am trying just the "w32tm /resync" line on its own. Yes, it > succeeds! Only this one line is needed: >=20 > w32tm /resync >=20 > All the other lines are unneeded for my problem. >=20 > My big question is why the "Update Now" button in the Windows user > interface is not doing this. >=20 > -- > Joe >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D105hix > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: <sl...@bl...> - 2005-04-26 22:04:05
|
Sam Moffatt <pa...@gm...> writes: > In regards to coLinux getting the time from Windows, it only does this > when booting when it mentions "Setting system clock from hardware > clock" or similar. This is when coLinux checks Windows. After this > point, it keeps its own time (which accounts for why there can be a > discrepency). How does coLinux set its time when the machine has just been powered on and resumes from hibernation? It can't keep time while the machine is powered off, and resuming from hibernation is obviously not the same as booting. So what does it do? -- Joe |
From: Nuno L. <li...@xp...> - 2005-04-26 22:27:22
|
[26-04-2005 23:02, Joe Wells (reverse mailbox letters only for non-public replies) escreveu] > Sam Moffatt <pa...@gm...> writes: > >>In regards to coLinux getting the time from Windows, it only does this >>when booting when it mentions "Setting system clock from hardware >>clock" or similar. This is when coLinux checks Windows. After this >>point, it keeps its own time (which accounts for why there can be a >>discrepency). Well, not exactly. That operation is more of a no-op. > How does coLinux set its time when the machine has just been powered > on and resumes from hibernation? It can't keep time while the machine > is powered off, and resuming from hibernation is obviously not the > same as booting. So what does it do? CoLinux uses a windows timer to update it's internal timer counters, but there are issues with the current aproach, and that's why it looses some "ticks". When it hibernates, it just updates it's timer on startup (or in the next few miliseconds). It's a piece of code that needs some more work, but you can use a ntp daemon in colinux to make it more "stable" (if it is very important for you). Regards, ~Nuno Lucas |
From: <sl...@bl...> - 2005-04-28 15:36:32
|
Nuno Lucas <li...@xp...> writes: > [26-04-2005 23:02, Joe Wells (reverse mailbox letters only for > non-public replies) escreveu] > > > Sam Moffatt <pa...@gm...> writes: > > > >> In regards to coLinux getting the time from Windows, it only does this > >> when booting when it mentions "Setting system clock from hardware > >> clock" or similar. This is when coLinux checks Windows. After this > >> point, it keeps its own time (which accounts for why there can be a > >> discrepency). > > Well, not exactly. That operation is more of a no-op. Can you explain what you mean by "that operation"? And in which sense is it a "no-op"? > > How does coLinux set its time when the machine has just been powered > > on and resumes from hibernation? It can't keep time while the machine > > is powered off, and resuming from hibernation is obviously not the > > same as booting. So what does it do? > > CoLinux uses a windows timer to update it's internal timer counters, but > there are issues with the current aproach, and that's why it looses some > "ticks". > > When it hibernates, it just updates it's timer on startup (or in the > next few miliseconds). Do you mean that coLinux asks Windows for the time each time the machine resumes from hibernation? Is there some way to detect when the machine coLinux is running on has resumed from hibernation? It seems I need to run NTP to keep the time accurate on coLinux. It seems I should not use Windows on the same machine as the NTP server for coLinux, because for some unknown reason Windows is failing to keep the time accurate (despite being configured to use NTP from an external NTP server). Because coLinux seems to be consulting Windows for the time each time the machine resumes from hibernation (and Windows has the wrong time!), I want to make sure an NTP resynchronization takes place shortly after each time the machine resumes from hibernation. So I need to use a completely external NTP server for coLinux. I don't want to deluge the external server with NTP requests every few minutes. But I don't currently know any other way to ensure an NTP request occurs shortly after each time the machine resumes from hibernation. Help? -- Thanks, Joe |
From: Nuno L. <li...@xp...> - 2005-04-28 16:54:07
|
[28-04-2005 16:35, Joe Wells escreveu] ... >>>>In regards to coLinux getting the time from Windows, it only does this >>>>when booting when it mentions "Setting system clock from hardware >>>>clock" or similar. This is when coLinux checks Windows. After this >>>>point, it keeps its own time (which accounts for why there can be a >>>>discrepency). >> >>Well, not exactly. That operation is more of a no-op. > > Can you explain what you mean by "that operation"? And in which sense > is it a "no-op"? I'll try to clarify below. It's not important, anyway... >>When it hibernates, it just updates it's timer on startup (or in the >>next few miliseconds). > > Do you mean that coLinux asks Windows for the time each time the > machine resumes from hibernation? CoLinux asks windows for the time a lot of times per-second. That is one of the things that can be improved. When it resumes from hibernation is only one more time it does the same, as colinux doesn't know (or cares) it was awaken from hibernation. It's not easy to explain the mechanism, and it's known to be broken in some cases (sometimes a clock skew happens, i.e. the timer goes back some milliseconds), but that's just one more thing that needs a fix in colinux (and that most users don't care much). > Is there some way to detect when the machine coLinux is running on has > resumed from hibernation? It seems I need to run NTP to keep the time > accurate on coLinux. It seems I should not use Windows on the same > machine as the NTP server for coLinux, because for some unknown reason > Windows is failing to keep the time accurate (despite being configured > to use NTP from an external NTP server). Because coLinux seems to be > consulting Windows for the time each time the machine resumes from > hibernation (and Windows has the wrong time!), I want to make sure an > NTP resynchronization takes place shortly after each time the machine > resumes from hibernation. So I need to use a completely external NTP > server for coLinux. I don't want to deluge the external server with > NTP requests every few minutes. But I don't currently know any other > way to ensure an NTP request occurs shortly after each time the > machine resumes from hibernation. Well, I would say that the current colinux state is not going to help you much in this respect. It is a part of the code that needs a more robust implementation. I don't see a reason for a NTP client not work ok in your case, and I don't think the network bandwidth wasted would be too great, but can't help you much there. Remember that colinux is not in a production stage yet ;) Regards, ~Nuno Lucas |
From: <sl...@bl...> - 2005-04-28 17:13:06
|
Nuno Lucas <li...@xp...> writes: > CoLinux asks windows for the time a lot of times per-second. I'm confused. If this is true, how is it possible that coLinux and Windows can report times that are different? For example, my coLinux is 50 seconds behind the host Windows right now. > I don't see a reason for a NTP client not work ok in your case, and I > don't think the network bandwidth wasted would be too great, but can't > help you much there. How could NTP possibly work on coLinux if coLinux is simply going to ask Windows for the time within less than a second? NTP could only fix the time for a fraction of a second before it was wrong again due to getting it from Windows (which has the wrong time on my machine). -- Joe |
From: Nuno L. <li...@xp...> - 2005-04-28 18:31:20
|
[28-04-2005 18:12, Joe Wells escreveu] > Nuno Lucas <li...@xp...> writes: >>CoLinux asks windows for the time a lot of times per-second. > > I'm confused. If this is true, how is it possible that coLinux and > Windows can report times that are different? For example, my coLinux > is 50 seconds behind the host Windows right now. Well, it's not easy to answer. There are different times in a system: the wall clock time (RTC), the time since boot (system time) and the timer tick count (jiffies). One can also get a high frequency counter value to measure small elapsed time durations. Let's just say that the wall clock time in colinux is from windows (what colinux thinks is the value of a "virtual" real time clock - RTC) and there is some tricky code to make all other values to be sane. There are also different syscalls for getting the different timer values and when you adjust the system time you only adjust it in the kernel, not in the ("virtual") hardware (that is the job of the shutdown script that fails trying to update the real time clock). >>I don't see a reason for a NTP client not work ok in your case, and I >>don't think the network bandwidth wasted would be too great, but can't >>help you much there. > > How could NTP possibly work on coLinux if coLinux is simply going to > ask Windows for the time within less than a second? NTP could only > fix the time for a fraction of a second before it was wrong again due > to getting it from Windows (which has the wrong time on my machine). I'm not an expert here (I'm a kernel newbie), and I'm probably saying some things not quite right because I'm not checking the linux kernel code, but I think you now understand that colinux can have a different time than windows. Besides, it's easy to test. Just set your windows clock with colinux running and you'll see colinux time stays the same. A detailed explanation of all this is beyond the scope of a simple mail answer, and the linux kernel is also changing this over time. Regards, ~Nuno Lucas |
From: Robert K C. Jr - I. F. D. C. <bco...@in...> - 2005-04-27 12:14:30
|
>Now I am trying just the "w32tm /resync" line on its own. Yes, it succeeds! Only this one line is needed: > w32tm /resync Joe, Keep in mind that the script I sent only needed to be run once. After that, assuming you have valid and reliable NTP servers, you should never need to /resync. In my experience Windows 2000/XP/2003 keep reliable time with NTP configured correctly. - Bob Coffman |
From: <sl...@bl...> - 2005-04-27 15:41:18
|
"Robert K Coffman Jr - Info From Data Corporation" <bco...@in...> writes: > >Now I am trying just the "w32tm /resync" line on its own. Yes, it > succeeds! Only this one line is needed: > > > w32tm /resync > > Joe, > > Keep in mind that the script I sent only needed to be run once. After that, > assuming you have valid and reliable NTP servers, you should never need to > /resync. In my experience Windows 2000/XP/2003 keep reliable time with NTP > configured correctly. I thought I had NTP configured correctly, but my machine has not been keeping reliable time! The "w32tm /resync" command at least lets me resynchronize the Windows time via NTP by hand. I am still worried the Windows time will get out of sync again, which is why I want to understand how to correctly keep the coLinux time correct without relying on the Windows time being correct. -- Joe |
From: CoLinux505 <col...@z5...> - 2005-04-27 06:50:31
|
| It's a piece of code that needs some more work, but you can use a ntp | daemon in colinux to make it more "stable" (if it is very important for | you). But, if he is late for an appointment, he will have an excuse. Non-CoLinux related: I've had problems with Windows, for whatever reason, keeping time in general. I don't think it is the motherboard, or batterry (replaced it). Out of the systems I used for years, about 3 of them didn't keep time when I used the computer intensively. They'd lose a few hours or minutes once in a while, even while turned on. It seemed to be more noticeable when the CPU was high for a few hours, but that could be coincidence. Lars |
From: CoLinux505 <col...@z5...> - 2005-04-27 09:03:46
|
Is bridged connection needed for apache? Somehow TAP can work with apache? (we could add these to the wiki too) |
From: Yaroslav F. <jar...@li...> - 2005-04-27 09:37:14
|
On Wed, Apr 27, 2005 at 02:59:14AM -0700, CoLinux505 wrote: > Is bridged connection needed for apache? > > Somehow TAP can work with apache? > If this is an interface to which TCP/IP sockets can be bound, Apache can work with it. Otherwise, it won't. Since TAP is ultimately for TCP/IP and acts like any other network interface in Linux (and in Windows), I don't think this question is worth any further discussion. -- X Windows: Accept any substitute. |
From: Sam M. <pa...@gm...> - 2005-04-27 12:08:10
|
windows time has noticeable frozen for me at times during high cpu too. its due to windows missing some messages here and there. On 4/27/05, CoLinux505 <col...@z5...> wrote: >=20 > | It's a piece of code that needs some more work, but you can use a ntp > | daemon in colinux to make it more "stable" (if it is very important for > | you). >=20 > But, if he is late for an appointment, he will have an excuse. >=20 > Non-CoLinux related: > I've had problems with Windows, for whatever reason, keeping time in = general. > I don't think it is the motherboard, or batterry (replaced it). Out of th= e systems > I used for years, about 3 of them didn't keep time when I used the comput= er > intensively. They'd lose a few hours or minutes once in a while, even whi= le turned > on. It seemed to be more noticeable when the CPU was high for a few hours= , but > that could be coincidence. >=20 > Lars >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Tell us your software development plans! > Take this survey and enter to win a one-year sub to SourceForge.net > Plus IDC's 2005 look-ahead and a copy of this survey > Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D105hix > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: CoLinux505 <col...@z5...> - 2005-04-27 10:16:50
|
Hrm, I must be missing some simple setting still, in the network somewhere. More specifically I want to connect from windows, and something went wrong ;( I can access locahost on Lynx browser within the coLinux console. The page loads up fine. Within Windows, I cannot access the IP address that is assigned to TAP, through a browser. Lars ----- Original Message ----- From: "Yaroslav Fedevych" <jar...@li...> |
From: CoLinux505 <col...@z5...> - 2005-04-27 11:25:30
|
Problem solved. Connect to 192.168.0.40 Don't know why I was trying 192.168.0.1 and 0.2 and 0.3, when that is not address of the coLinux server. Knock On Wood(ie). Well, for future people trying to set up apache... -always do a simple sanity check, by using "ifconfig" command from within coLinux. -Eth0 then will tell you the IP (usually 192.168.0.40 for coLinux) -the ip address is also in the /etc/network/interfaces section, where you may have custom defined settings. Duh. Now I can get back to local testing, and connecting to FTP through midnight commander, and etc. I think midnight commander sessions using alt-arrow will be my blue "x-window system" for coLinux. The project is as follows: hack MC up to act more like total commander, the keys are just all wrong ;-) Lars ----- Original Message ----- From: "CoLinux505" <col...@z5...> To: <col...@li...> Sent: Wednesday, April 27, 2005 4:12 AM Subject: Re: [coLinux-users] Apache: basic questions | Hrm, I must be missing some simple setting still, in the network somewhere. |
From: CoLinux505 <col...@z5...> - 2005-04-28 13:33:23
|
CoLinuxBatchFiles http://wiki.colinux.org/cgi-bin/CoLinuxBatchFiles CommandLineReference http://wiki.colinux.org/cgi-bin/CommandLineReference They need some filling in, I'll be working on them, and formatting of them could be improved so they look better Regards, Lars p.s. are some pages, like the table of contents only editable by one person, the admin? |