Hi, My client is a Suse 9.2.... When I run this command to connect a Suse Linux 9.2 server to show tape drive status .. # mt -f root@server1:/dev/nst0 status drive type = Generic SCSI-2 tape drive status = 838861312 sense key error = 0 residue count = 0 file number = 0 block number = 0 Tape block size 512 bytes. Density code 0x32 (unknown). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN All works fine.. But the same command to connect to a Suse 10, the command failed: # mt -f root@server2:/dev/nst0 status mt: root@server2:/dev/nst0 No status are given and the command exists with status 1 The .rhosts file are the same on server with Suse 92 and Suse 10 When I run the same command above in a client with Suse 10 to connect to a server 9.2 or 10.0, this errors given: mt: microsiga2:/dev/nst0: I/O error What's wrong??
rejaine@bhz.jamef.com.br wrote:
But the same command to connect to a Suse 10, the command failed:
# mt -f root@server2:/dev/nst0 status mt: root@server2:/dev/nst0
No status are given and the command exists with status 1
The .rhosts file are the same on server with Suse 92 and Suse 10
When I run the same command above in a client with Suse 10 to connect to a server 9.2 or 10.0, this errors given:
mt: microsiga2:/dev/nst0: I/O error
What's wrong??
Do you use ssh or rsh to connect? (option --rsh-command of "mt") If you use rsh: Is rshd installed on the Suse systems? -- Viele Grüße ------------------------------------------------------------------------ Michael
If I use "mt -f server:/dev/st0 status" from Suse 9.2/10.0 to a Suse 10.0, don't work.. (exit with status 1) But if I use "rsh server mt -f /dev/st0 status" from 9.2/10.0 to a Suse 10.0, all works fine (exit with status 0) and all status are given .. The first command works fine if I do it from Suse 9.2/10.0 to another Suse 9.2.. But not work from Suse 10 to another Suse 10... Em Qui, 2006-03-09 às 08:46 +0100, Michael Behrens escreveu:
rejaine@bhz.jamef.com.br wrote:
But the same command to connect to a Suse 10, the command failed:
# mt -f root@server2:/dev/nst0 status mt: root@server2:/dev/nst0
No status are given and the command exists with status 1
The .rhosts file are the same on server with Suse 92 and Suse 10
When I run the same command above in a client with Suse 10 to connect to a server 9.2 or 10.0, this errors given:
mt: microsiga2:/dev/nst0: I/O error
What's wrong??
Do you use ssh or rsh to connect? (option --rsh-command of "mt") If you use rsh: Is rshd installed on the Suse systems?
--
Viele Grüße
------------------------------------------------------------------------ Michael
rejaine@bhz.jamef.com.br wrote:
If I use "mt -f server:/dev/st0 status" from Suse 9.2/10.0 to a Suse 10.0, don't work.. (exit with status 1)
But if I use "rsh server mt -f /dev/st0 status" from 9.2/10.0 to a Suse 10.0, all works fine (exit with status 0) and all status are given ..
The first command works fine if I do it from Suse 9.2/10.0 to another Suse 9.2.. But not work from Suse 10 to another Suse 10...
Maybe you need "rmt" (remote magnetic tape protocol server) on the server, which is in the package "star". -- Viele Grüße ------------------------------------------------------------------------ Michael
participants (2)
-
Michael Behrens
-
rejaine@bhz.jamef.com.br