RS/6000 RSUD COMMAND IN 3.2 BLOCK SIZE
ITEM: RTA000025677
QUESTION:
1. Customer is using rsud command. The command sets a block size on
the tape drive to 512 and leaves it this way. Certainly this should
not be a normal circumstance¢ Can you please verify that the rsud
command should reset the block size? If this is normal, please
explain any rational, if not, I'll have the customer pursue
with software defect support.
2. Customer did network install upgrade from 3.1.5 to 3.2 of their
name server. The name server deamon runs for about 15 minutes and
then goes to twilight zone. A stopsrc on named also goes to twilight
zone. SIGHUP to pid kills and then startsrc on named is o.k. but
named dies after 15 minutes again. One askq article mentions a
conflict between NIS and name server in 3.2. This customer does not
use nfs at all but did do the nfs export setup as detailed in the
installation manual for network installs. Could this export nfs mount
be hosing up the name server?
---------- ---------- ---------- --------- ---------- ----------
A: In the rsud script, the cleanup routine:
clean_up () {
trap "" EXIT HUP INT QUIT TERM
rm -f $UPGRADE_TMP/rsud.data.1
$_CALL_RESET_TAPE
. -z "$_exitexit" . && exit 11
Should return the tape drive back to the original block size
setting. I agree that if it is not working this way, you
should report this to Defect Support.
As far as the named dying, I have found an APAR that references
this problem. Please reference APAR IX23937 to obtain the fix for
the named problem.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q600585 BQMXK
Additional search words:
BLKD BLOCK BQMXK CMD COMMAND INSTALL INSTALLATION IX NAMESERVER
NETWORK NETWORKING NSRV OCT92 OP OZNEW PROBLEM RISCOSO RISCSYSTEM
RSUD SIZE SIZING SOFTWARE SYS TP UPGRADE 3.1 3.2
WWQA: ITEM: RTA000025677 ITEM: RTA000025677
Dated: 11/1996 Category: RISCOSO
This HTML file was generated 99/06/24~12:43:09
Comments or suggestions?
Contact us