Tru64 binerrlog renewing

[Francesca Watts]

Hello...

After renewing the binary.errlog using the below method. The FRU firmware details are not in place. Is there a way of adding the boot record, without rebooting?


9.2.2.1.3.2 Clear the Log with binlogd Running
For version 5.1A or higher, follow these steps on each cluster node that you want to clear:
1. Verify the binary.errlog CDSL section is complete as previously described.
2. If desired, keep any previously saved copy from being overwritten by moving it to any appropriate
name, for example:
# cd /var/cluster/members/member/adm/binlog.saved
# mv binary.errlog.saved binary.errlog.2002_06_11
3. Cause binlogd to copy and clear the original error log:
# kill -USR1 `cat /var/run/binlogd.pid`
The previous command does not kill the binlogd process. Instead, it sends a signal to binlogd that
causes it to copy /var/adm/binary.errlog to /var/cluster/members/member/adm/binlog.saved. Then,
the original /var/adm/binary.errlog file gets recreated with only a configuration event. Note that
/var/adm/binary.errlog is a CDSL that points to /var/cluster/members/{memb}/adm/binary.errlog

[Ivan Ferreira]

I'm not sure of the information that you need, but the header of the collect tool gives you the server model, memory, cpu family, boot time, etc.

[Francesca Watts]

Thanks for the reply.

Yes ill have a look at the collect output. Was specifically intrested in teh firmware revisions. Looks like consvar can do that for me. Ill have a look at the collect file too.

Many thanks!

Francesca