error while converting to trusted system

[ian_60]

I converted our HP_UX 11.0 system to a trusted system today, whilst doing this the SAM window come up with an error "The attempt to convert this system to a trusted system failed. The command" - the rest of the error was truncated.
However on exiting SAM it was soon clear the system had converted and my system was now trusted, and seems to behaving as a trusted system should.
Should I concern myself with the error, is there a log of the conversion?
Also I want to specify authorized login times for my users, is there a quick way to do this or do I have to do this individually thought SAM?

Thanks in advance,
Ian

[doug mielke]

try /var/sam/log/samlog

[Robert-Jan Goossens]

Hi Ian,

System will not convert to trusted
DocId: USECKBRC00007628 Updated: 8/2/01 7:36:00 AM
PROBLEM

The system will not convert to a trusted system through SAM. This message
appears in the SAM Log:

http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062922665

Hope it helps,

Robert-Jan.

[blal]

Hi

There may be some problem in converting a particular user database.

You can avaoid this error.

execute the command

/usr/lbin/tsconvert

and see that you are getting tyhe following output.
"System has already been converted."

[Steven E. Protter]

pwchk
grpchk

Something might have been wron with /etc/passwd before the conversion.

If you can't convert on the command line, I'd back out the change.

SEP

[ian_60]

Looking in the SAM log it seems to be complaining about the presence of the file root.safe (backup taken before root cron updated) in /var/spool/cron/crontabs (extract from log attached).
Do I need to take any action as part from this error the system has converted successfully?

Many Thanks,
Ian

[Robert-Jan Goossens]

Hi,

The owner of that job has to be changed. If it where me I would change the ownership, untrust the damned thing again, trust it again. Just for my I own peace of mind.

My 2c,

Robert-Jan.

[Darren Prior]

Hi Ian,

In future, it would be better to use crontab -l and redirect the output to a file somewhere separate from the /var/spool dirs. I've seen problems recently where people tried to run crontab on files in these dirs to resubmit them which leads to unpredictable results.

regards,

Darren.

[ian_60]

Thanks for the replies, I decided to untrust the system, move the offending files in the crontabs directory and run the process to convert to trusted again - just for peace of mind. This time it ran without errors.