OK, it sound like our different experiences, esp. different platforms, are giving us different results, hence our different interpretations of the original post.
I'm new to NistNet, and decided to try the non-modularized versions first (on RedHat Enterprise Server 4), since it was the simplest thing do. It worked, hence I haven't bothered to modularize. I do agree that modularization is "probably" the "right" solution, though I haven't tried it, so I can't speak with any authority on that score. But at least in the one case I have tried, I can confirm that NistNet does work with non-modularized RTC on RHES4, and that Deepanshu's original warning msg can be ignored (for the purposes of a usable NistNet), provided the information in README.Clock is taken into account. -----Original Message----- From: David Morris [mailto:[EMAIL PROTECTED] Sent: Sunday, July 30, 2006 6:30 PM To: Walter Tuvell Cc: nistnet@antd.nist.gov Subject: RE: [nistnet] NISTnet not working properly Well, on slackware specifically, w/o a modularized RTC such that nistnet can replace it, NISTNet did not work correctly. I nolonger recall the specific symptoms. Based on following this list for > 2.5 years and listening to many problems as well as my own problems, resolved by rebuilding the kernel with modularized RTC, I would conclude that the proper solution is to modularized RTC. Hence my initial response. I would guess that under some circumstances, nistnet's takeover of the RTC isn't 100% successful if the existing RTC isn't removed. As I said, from my experienced, and from others posting to this list, the RTC problem should be resolved with a proper kernel. On Sun, 30 Jul 2006, Walter Tuvell wrote: > Maybe we're talking about different things? I'm not sure what you mean > by "the NistNet RTC module"? I've been referring to the standard Linux > RTC module, /dev/rtc, as documented in > http://slackware.osuosl.org/slackware-8.0/docs/linux-2.4.5/rtc.txt. > > > > Of course NistNet won't work if /dev/rtc doesn't exist. But that's not > what's under discussion. What's being discussed is the warning msg > Deepanshu posted (repeated below), regarding whether or not the RTC > should be *modularized*. And that's addressed by README.Clock. > > > > I have not modularized the RTC, so I get this warning message too, yet > NISTnet runs just fine (using the regular, non-modularized, /dev/rtc). > This isn't a problem for me because the machine is captive (used only > for NISTnet, not other apps), and the known side-effects on the hwclock > calls in rc files can be fixed per README.Clock. > > > > /* > > For reference, here's the original warning msg posted by Deepanshu: > > > > > rmmod: module rtc is not loaded > > > Couldn't find rtc module - > > > /dev/rtc will be mostly unusable after running istnet. Sorry about > > > that..... > > > To prevent this message recompile rtc (Enhanced Real Time Clock > > > Support, under character devices) as a module. > > */ > > > > > > > > -----Original Message----- > From: David Morris [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 29, 2006 6:05 PM > To: Walter Tuvell > Cc: nistnet@antd.nist.gov > Subject: RE: [nistnet] NISTnet not working properly > > > > > > I see nothing in the README.Clock file which suggests that NistNET will > > run correctly if the NistNet RTC module isn't installed. The NistNet RTC > > is required and that is the point of the error message which started > this > > thread. My post was terse ... fix the RTC issue. The install > instructions > > are clear, the kernel must be built with a modular RTC. The NistNet RTC > is > > compiled as part of the NistNet make. > > > > On Sat, 29 Jul 2006, Walter Tuvell wrote: > > > > > I agree with what you've said here, except for our interpretations of > > > the initiating note. What that suggested to me was that the user was > > > merely running with a non-modularized RTC. In that case, README.Clock > > > indicates NISTnet will work correctly, but other apps might be > > > negatively impacted. > > > > > > > > > -----Original Message----- > > > From: David Morris [mailto:[EMAIL PROTECTED] > > > Sent: Friday, July 28, 2006 5:21 PM > > > To: Walter Tuvell > > > Cc: deepanshu sandhuria; nistnet@antd.nist.gov > > > Subject: RE: [nistnet] NISTnet not working properly > > > > > > Finally back to my nistnet system. > > > > > > I see nothing in README.Clock which suggests you don't have to use the > > > Nistnet RTC module. Based on my experience, if you don't have a kernel > > > built with RTC in a module (either you rebuild the kernel or your > > > distribution comes that way) and haven't compiled a RTC module for > your > > > system, NistNet will not operate correctly. > > > > > > The message which started this thread suggested to me that the RTC > > > setup was incorrect. > > > > > > According to the system version files, I'm running nistnet on RH EL > > > WS3u0. > > > This is a 2.4.21-4 Redhad kernel customized for modular RTC. > > > > > > Dave Morris > > > > > > On Wed, 26 Jul 2006, Walter Tuvell wrote: > > > > > > > Are you sure? README.Clock seems to indicate otherwise, and > > > experience > > > > seems to show the README.Clock is right about that. > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] On Behalf Of David Morris > > > > Sent: Wednesday, July 26, 2006 3:51 PM > > > > To: deepanshu sandhuria > > > > Cc: nistnet@antd.nist.gov > > > > Subject: Re: [nistnet] NISTnet not working properly > > > > > > > > > > > > > > > > On 26 Jul 2006, deepanshu sandhuria wrote: > > > > > > > > > > > > > I am new to Linux and dont know what affect this warning may have > on > > > > > running Nistenet. > > > > > > > > Simple, NISTNET won't work if you don't fix the RTC issue. > > > > > > > > _______________________________________________ > > > > nistnet mailing list > > > > nistnet@antd.nist.gov > > > > http://www-x.antd.nist.gov/mailman/listinfo/nistnet > > > > > > > > > _______________________________________________ nistnet mailing list nistnet@antd.nist.gov http://www-x.antd.nist.gov/mailman/listinfo/nistnet
