Re: Beacon 0.9.58
Hi, Andrew,
> I notice that "CST" is hardwired into the beacon code for the time
> display. In fact, I think it's localtime, so it would be CDT in the summer
> and CST in the winter. Also, it's wrong when the beacon is not a master.
That's one of those "Oh, yeah -- I should fix that" things. Thanks for the
reminder. ;-)
> Perhaps it would be easier to just use gmtime() and use UTC everywhere ...
> :-) (getting tm_isdst out of localtime() and figuring what zone and
> acronym to use seems a nightmare cross-platform ...)
I think UTC is probably the way to go (unless anyone else has strong
opinions on the matter?), especially given how widespread (geographically
speaking) current Beacon usage already is, much less will become over time.
> Re. burst mode, I enabled it and ran the beacon as
> $ beacon > beacon.log &
> I don't recall stopping it (but it was started from an xterm on a PC that
> lost power ...) but found it stopped cleanly today, after making a 20Mb
> logfile. Is the big logfile normal, or a result of burst mode ? Since
> restarting, I don't see anything similar.
The only messages you should ever see from a happy Beacon are the two line
"Just ran a Burst/Silence test" messages, and any Timeout Deletes of
Beacons that the Central Server hasn't heard from for over five minutes.
Should be very minimal output on the command line.
So, yes, a big logfile would be unusual. What was in the file?
Mitch
--
Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
Project: http://dast.nlanr.net/ | Personal: http://hobbes.ncsa.uiuc.edu/