errors msg on syslog cause sam errors...

[hpuxhelp]

an 29 11:23:30 kunu syslog: get_pwhist_config)): Password
history is not con
figured in the /etc/default/security file. Default password history
depth 1 is
used.
Jan 29 11:23:33 kunu syslog: files_getprpwhist: Failed to lock
pwhist file.
Jan 29 11:23:33 kunu syslog: update_passwd_entry: Failed to
obtain password h
istory information
sam
The file "/var/sam/lock/lock_tc" could not be locked (errno = 45,
"Lockf deadlock detection"). This file must be lockable so that this
SAM session can be locked. Otherwise, other SAM sessions won't be able
to detect that this SAM session is running on the system.

I have trying to delete that file in /var/sam/lock
however i was still unable to fix this proble

[Steven E. Protter]

Your error message does not appear to have anything to do with your sam problem in your other post.

Fortuneately it does tell you how to resolve it.

It would seem this system is trusted, so you can either follow the instructions in the error log, or sue sam

auditing and security policies
system security policies to set such parameters.

The choice is yours.

You probably want to follow the manaul instructions in the error log because it would appear sam will be hosed until you delete the lock file.

P

[Robert-Jan Goossens]

Hi,

check the man page of security

http://devrsrc1.external.hp.com/STKLI/man/11iv1.5/security_4.html

Robert-Jan.