07-02-2007
"The first one can be tested by trying to run 'pwd', eg 'rsh -n server pwd'. "
We seem to have a problem here from server 2 as root I can rsh to Server3 but not Server1
However from Server3 I can rsh to both Server1 and Server2
/etc/hosts on each machine has entries for the others
/.rhosts on each server has entries for the other servers
What else would be controlling ability to rsh??
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was recently given the responsibility of the unix box at our work. Without much training, I now have to go back and restore a file from tape. I'm having some trouble with it. I'm getting an error with the blocksize.
The part of the script that does the tar looks like this:
tar cvfX... (11 Replies)
Discussion started by: citrowske
11 Replies
2. Shell Programming and Scripting
Hi,
Would appreciate if anyone could tell me if it is possible to mount (and use) a remote tape drive on a AIX server, and if so, what are the precise configuration steps needed?
The tape drive to be mounted as a remote tape drive is present on another AIX server in the same network.
... (0 Replies)
Discussion started by: dnicky
0 Replies
3. AIX
Hi,
Would appreciate if anyone could tell me if it is possible to mount (and use) a remote tape drive on a AIX server, and if so, what are the precise configuration steps needed?
The tape drive to be mounted as a remote tape drive is present on another AIX server in the same network.
... (5 Replies)
Discussion started by: dnicky
5 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
I have kinda inherited this problem, but was wondering if anyone else had any ideas.
Currently all our backup rentention periods are set to 2 weeks, so that we can cycle through tapes (save money etc...). Anyhow the guys next door in IT, decided one day long long ago, that it would... (0 Replies)
Discussion started by: B14speedfreak
0 Replies
5. Solaris
hello guys,
am trying to save a file file1 to a remote tape drive using tar and i get a permission denied error as shown below:
server1%tar cvf - file1 | rsh server2 dd of=/dev/rmt/1m conv=sync
a file1 1883905K
permission denied
since server2 requires login username and password, i see in... (3 Replies)
Discussion started by: nom
3 Replies
6. UNIX for Dummies Questions & Answers
We have 2 UNIX machines,
1.HP-UX 11i where oracle database running on it.
2.AIX 5 with Ultrium LTO3 tape drive connected.
My query is, i want to send oracle database archive files from HP machine to the tape drive which connected on AIX machine, everyday.
These files should be appended.
I... (3 Replies)
Discussion started by: yashdbad
3 Replies
7. Solaris
Hello all,
I'm trying to backup some files on a solaris 10 machine to the remote tape drive connected to another solaris 10 machine.
I have set up rsh to allow for password-less connection between the servers, but I'm not able to write to the tape with the command:
root@sdp4a>tar cvf... (1 Reply)
Discussion started by: kerrygold
1 Replies
8. UNIX for Advanced & Expert Users
Good day all!
I need to recover FS from backup, but the thing is that tape drive cable is not compatible with the server's input (tape drive's cable is wide, but at the server input (V240) is tight one). So, I want to connect this tape drive to another Solaris based server and mount tape drive... (3 Replies)
Discussion started by: nypreH
3 Replies
9. Shell Programming and Scripting
hi all ,
a messages appeared to me when i was checking my /var/adm/messages
and the below code was in it
Oct 6 13:15:21 medprod scsi: /pci@3,700000/SUNW,emlxs@0/fp@0,0/st@w21000024ff305234,7 (st1):
Oct 6 13:15:21 medprod Restoring tape position at fileno=320,... (5 Replies)
Discussion started by: semaan
5 Replies
10. UNIX for Dummies Questions & Answers
Hello everyone.
I googled a little bit, and the best anwers i had were found in this forum. But , unfortunately, they couldn't give me a solution. So i decided to ask the question completely.
I have two servers:
One RHEL 5 , x64 , with a SCSI DAT72 Tape Drive.
Another (the new one), with... (0 Replies)
Discussion started by: pablobhz
0 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)
DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)