swacl and users other than root

[Armin Kunaschik]

Hm... looks like your IPD is not in the best condition. Please remove the mentioned block manually from INDEX for testing. What errors/warnings is "swverify \*" displaying now?

My 2 cents,
Armin

[Bob E Campbell]

I would advise caution here. It is possible that there is minor corruption of the IPD and the system is fine but it is just as likely that there is true system corruption of one type or another.

A full backup followed by a cold-install of the system will get you back to a known good state. While this is a big hit, I *really* love known good states.

If that is not an option you might want to contact HP support. I have faith in my skills, but would not choose to do brain surgery without system access...

That said, if you want to continue start with posting the /var/adm/sw/swagent.log for the command "swverify \*".

[Peter Biron]

:/var/adm/sw $grep -i swverify swagent.log|more
* File "/usr/sbin/swverify" could not be removed. It was renamed
* File "/usr/sbin/swverify" could not be removed. It was renamed
* File "/usr/sbin/swverify" could not be removed. It was renamed

I did not expect that. What does that mean?

[Peter Biron]

Maybe we should start over here. All the functionality of the SW commands work fine - as long as I am root. If I become any other user I get seg faults and memory errors. This would leave me to believe the commands and system all seem to work UNLESS I try as a non-root user. Commands as root all work as advertised. Sorry if that wasn't clear before. That said I did reinstall the SD suite with the reinstall option set to true. Same boat. I'm thinking it HAS to be some kind of permissions issue. How do I make sure all the perms are correct? Thanks.

[Bob E Campbell · Accepted solution]

Do not worry about those swrverify messages, they are normal. If a file is busy during an installation it is moved out of the way and removed at a later time. The sw* commands are all hardlinked and should be expected to be busy during a swinstall.

What does the swagent.log show after a "swverify \*" command? That will find any permissions problems and/or broken dependencies or corruptions.

[Peter Biron]

OK Bob - I think u may have nailed the problem. Now I have to find the solution. swverify does have a slew of errors in it. A lot of them are about missing fonts but numerous perm problems exist also. Bastille was run on this system as part of a CIS effort. I'm guessing that's where it may have started. I'll have to go through the list and that may take a while. The list is to long to post so I'll hack at it for now and get back at you. Thanks for the lead......