10 Aug
2015
10 Aug
'15
6:23 p.m.
On 2015-08-10 18:15, Brian Schenkenberger, VAXman- wrote:
That is pretty funny.
Anyway, I now have the 5.3-184 version PCSI file on the machine. Now I
just need to install it. Later... TCPIP turned off at the moment, to
keep things calm.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Johnny Billquist <bqt at softjar.se> writes:
I wasn't trying to imply anything else. :-)
I just felt that a batch job for something the system could do for me
automatically seemed like a suboptimal solution, and wanted to point it out.
On 2015-08-10 16:55, Brian Schenkenberger,
VAXman- wrote:
Well, you're getting an implicit purge each time a new file is created with
a version limit. Probably much better than filling up a directory with log
files and then, purging but you're still purging. Johnny Billquist <bqt at softjar.se>
writes:
Agree. But besides, I do not (so far) have excessive number of
generations of log files in the first place. I just felt that if I
wanted to keep the number of kept generations low, I would just put a
limit on them instead of having a batch job run regularly that did a
purge... Well, if I wanted then, even easier is to just
set a version limit on=20
the files. :-)
Both your solution (version limits) and the periodic batch job purge will
not stop the unnecessary log file I/O, and both add to disk I/O and file
system activity. If this is a known problem with V5.1 and it's fixed in
V5.3, I'd suggest that you obtain that patch/version/eco and install it.
I, personally, loathe solutions to problems that elicit other problems or
increase resource loads. But the known
problem in 5.1 that I was referring to was the total
failure of the telnet daemon, by which is just spews 0xff after
something manages to corrupt it. I also have a full disk, which I yet do
now know for sure why.
I had a client hit 32,767 on the day of the Mayan apocalypse. It wasn't the
end of the world but it was the end of their production for that day. ;) FYI, eventually, your version limit solution will
require intervention as
you inevitably crash and burn when you hit ;32,767.
That is also true.