From: Chiu, PCM \(Peter\) (P.C.M.Chiu@rl.ac.uk)
Date: Thu Apr 25 2002 - 11:05:37 EDT
Hi,
I have a look of the archive and understand this topic
has been discussed before.
I have a slightly different scenario and welcome for any input.
I have a DDS4 (1 drive, 6 slots) autoloader attached to an Tru64 Unix
server.
The vdump commands in a script work really fine when invoked
interactively on a terminal (at console). When it hits the end of
a tape, vdump waits until the next tape is loaded, and then carries on
without any human intervention.
I then put the script as a cron job, vdump now fails with an error:
vdump: Status at Thu Apr 25 13:06:00 2002
vdump: Dumped 16116081980 of 43487094064 bytes; 37.1% completed
vdump: Dumped 209 of 1624 directories; 12.9% completed
vdump: Dumped 5711 of 20207 files; 28.3% completed
vdump: out of space and unable to prompt input for new tape;
[25] Not a typewriter
The script then executes the next command.
So the question is, how to make vdump wait for the next tape.
It appears to be something to do with the redirection of standard input
that triggers this kind of behaviour.
Thanks.
PS. If you can, pls reply direct to me. I shall summarise your responses.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:39 EDT