/opt/VRTSob

[Fred Martin_1]

Just noticed these files on my system, are 'nouser' ... currently own by UID 4484 GID 119 ... what should the ownerships really be, am I missing a passwd entry or should they be owned by someone else?

/opt/VRTSob/jre/bin/.start_xfs
/opt/VRTSob/jre/bin/java
/opt/VRTSob/jre/bin/keytool
/opt/VRTSob/jre/bin/policytool
/opt/VRTSob/jre/bin/rmid
/opt/VRTSob/jre/bin/rmiregistry
/opt/VRTSob/jre/bin/tnameserv
/opt/VRTSob/jre/lib/PA_RISC/hotspot
/opt/VRTSob/jre/lib/PA_RISC/libmawt.sl
/opt/VRTSob/jre/lib/PA_RISC2.0/hotspot
/opt/VRTSob/jre/lib/PA_RISC2.0/libmawt.sl

[John Poff]

Hi,

Looks like they could be some files belonging to Veritas Enterprise Manager. Do you have that installed on your system?

JP

[Robert-Jan Goossens]

VRTSobâ VERITAS Enterprise Administrator Service

I don't have it on my HP's but I do have it on my sun's with the owner bin:bin.

Regards,
Robert-

[Fred Martin_1]

Only if it came installed with HP-UX 11i, Progress DB, or an NxTrend product. That's about all I've got on this server. I've heard of it but not familiar with it.

[Patrick Wallek · Accepted solution]

If you notice in the 'll' output for the items with the uid of 4484 as the owner, they are ALL links to another file. In this case, I wouldn't worry too much. I've got the same issue on my 11.11 machine.

# cd /opt/VRTSob
# find . -user 4484 -exec ll -d {} \;
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/.start_xfs -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/java -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/keytool -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/policytool -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/rmid -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/rmiregistry -> .java_wrapper
lrwxrwxrwx 1 4484 119 13 Nov 13 2003 ./bin/tnameserv -> .java_wrapper
lrwxrwxrwx 1 4484 119 6 Nov 13 2003 ./lib/PA_RISC/hotspot -> server
lrwxrwxrwx 1 4484 119 18 Nov 13 2003 ./lib/PA_RISC/libmawt.sl -> motif21/libmawt.sl
lrwxrwxrwx 1 4484 119 6 Nov 13 2003 ./lib/PA_RISC2.0/hotspot -> server
lrwxrwxrwx 1 4484 119 18 Nov 13 2003 ./lib/PA_RISC2.0/libmawt.sl -> motif21/libmawt.sl

[Fred Martin_1]

Ah, so they are. The fact that you have the same UID as me, is an indication that it's right from the install that way. Since they're links anyway and permissioned wide open I'm guessing that, for the sake of cleaning up, chowning them to root:sys wouldn't hurt.

[Victor_5]

Hi Fred:

I got the same result on my 11.i server, since it is created by installation by default, I don't suggest you to change them.

Actually, VRTSob is for Veritas VxVM GUI interface, on the server side, you need VRTSob, VRTSvmpro and VRTSfspro to make it work, but a lot of companies don't allow VEA GUI for security reason, if you don't need it, you can simply stop the service on the server side:

#vxsvc -k

Just my two cents.

[Fred Martin_1]

Thanks Victor, in fact I don't do anything GUI on this server, stopping it is a good idea.

[Fred Martin_1]

It appears that this software is started at boot by the script /sbin/rc2.d/S999isisd.

What is the proper way to prevent this from starting up at all?

[Pete Randall]

Fred,

Normally, there would be a file in /etc/rc.config.d/ called isisd. You would edit this file and tell it that you didn't want the daemon to start. Since Veritas chose not to play by the rules and supply this standard configuration file, I think the only way to prevent start up is to rm the link from /sbin/rc2.d/S999isisd to /sbin/init.d/isisd. You should also rm the corresponding kill link: /sbin/rc1.d/K999isisd.


Pete