nfs mounting the filesytem isn't a problem, this is what i was going to do if what i was trying to do with the index server didn't work.
the wierd thing about the hang is the only thing that changed was specifying an index-server other then the tape server. the dumps where written to tape, the index's where written but where still viewed as a temp file, they hadn't been moved to the file index. after seeing this i went back and reconfigured, recompiled, installed, and re-ran the dump and everything ran great. wierd behavior, but everything is running great now. thanks John R. Jackson wrote: >>... is it possible to write the indexes to another system like this? ... >> > > Not currently. It would take a pretty major change to the protocol. > It also has a number of error handling issues. > > Any chance your other machine could NFS export where you want to store the > index files to the tape server machine so it could write them that way? > I used to do a variation of that. > > None of this has anything to do with your hang. Specifying the index > server at ./configure time only sets a default for amrecover (which can > be changed on the command line). It has no other purpose. > > You probably need to look at the client to find out why the data is > not moving. > > >>Darin Perusich >> > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] > > -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED]
