[Info-vax] satellite one hour ahead

[mcleanjoh at gmail.com]

On Wednesday, October 26, 2016 at 12:17:31 AM UTC+11, John E. Malmberg wrote:
> On 10/25/2016 4:44 AM, Phillip Helbig (undress to reply) wrote:
> > In article <num3g3$kr7$1 at dont-email.me>, Stephen Hoffman
> > <seaohveh at hoffmanlabs.invalid> writes:
> >
> >> If you want to try localtime and lack the patches for the older bits,
> >> then upgrade to V8.4 --- you've been asked to perform that V8.4 upgrade
> >> before, and for other reasons --- and run with something approaching
> >> current OpenVMS bits, and see if that remediates this.
> >
> > Yes, underpatched, but I'm a hobbyist.  7.3-2 patches were current when
> > the access was cut off.
> 
> You should be able to compare the timezone files and the *time* logicals.
> 
> There also should be a utility installed that allows you to create 
> custom timezones, so that you can generate one.
> 
> Or if the node with an issue just has an out of date timezone file for 
> your location, I would be surprised if the timezone file from a working 
> has a different format.
> 
> > 8.4?  Upgraded one node and DECwindows stopped working in that the CDE
> > interface doesn't come up.  Since I use CDE daily (mostly on a satellite
> > booting from a 7.3-2 node), I can't risk that.
> >
> > When I have time I'll see if I can solve the DECwindows problem.  There
> > were many suggestions here, but none of them helped.
> 
> It is mostly DCL scripts.  Which means that you can temporarily add 
> instrumentation to them.
> 
> Also temporarily turn on image accounting to find out the exit status of 
> images that you can not see from the command files.
> 
> Or permanently turn on image accounting and have daily job that scans it 
> for events and starts a new log, with a retention policy on old logs 
> that makes sense for you.
> 
> Regards,
> -John
> wb8tyw at qsl.net_work

I'd like to see image accounting selectable per process and with output file names that by default include the username or parent PID. It could be very useful for trouble shooting or any situation where the logged data is applicable to some but not all users.

Privileged users could apply it to processes other than their own but unprivileged users only to their own processes.  

None of this should replace the system-wide accounting available now but be in addition to it.