You should append or enter the required X resources (nvevents.correlationRule,
but you may be interested in nvevents.saveDir, nvevents.loadEnvOnInit,
nvevents.saveEnvOnExit, nvevents.considerStaticWrkSpcs, etc. that are relevant
if you want the user's Nvevents environment to be saved on exit and reloaded at
startup) from /usr/OV/app-defaults/Nvevents to user's $HOME/.Xdefaults. Then,
after you modify them accordingly, the application should reflect the new
"Rauwers, Laurens" wrote:
> Using NV5.1.2 on DEC UNIX
> Sometime ago it was suggested here that you can startup nvevents with
> different rulesets per user.
> The only thing you have to do is modify the ruleset file in Nvevents and
> copy this file to the home directory of the user.
> You can guess what the problem is: nvevents is still taking the original
> Nvevents in /usr/OV/app-defaults as startup.
> NetView is started via a script in the $HOME of the user, and the nv6000.log
> is updated in this directory.
> Is there someone outhere who can point me to the right direction to solve
> this problem?
> Thanks in advance.
> Laurens Rauwers
> e-mail:rauwers AT hitt DOT nl
> NV-L List information (unsubscribing, policies, posting, digest version,
> searchable archives): http://www.tkg.com/nv-l