John, It looks like the RPM isn't the issue after all. That makes me happy. The ulimit command showed me that I had a 100Mb limit on any file size. I'll have to check it out, but my guess is that the Bastille hardening script did that for me. This was the first system that I had tried that on. I actually had to go into /etc/security/limits.conf to remove it, then log all the way out and back in again. Thanks so much for your help.
* John R. Jackson ([EMAIL PROTECTED]) wrote: > >I'll grab the source and compile if I have to, but I don't see > >why the RPM shouldn't work for me if it works for everybody else. > >(Sorry, just a little rant there) > > Agreed (although RPM's for Amanda have a lot of issues that are discussed > over and over on the mailing list). FWIW, the latest sources diagnose > this problem better, so when someone gets around to generating an RPM > from them this would have been easier to track down. > > >Anyways, I followed your instructions as best I could. ... > > You did great. Here's the problem: > > >Program received signal SIGXFSZ, File size limit exceeded. > > This says the dumper got an error from the OS saying it was not allowed > to write any more data because it had exceeded its file size limit. > > I don't know much about Linux, but I'd run "ulimit -a" as your Amanda > user and see what it says the limits are. It might also have something > to do with the specific holding disk file system, but I doubt that. > > I'm also not sure what you have to do to crank up the file size limit > for a user. It would probably be some accounting thing. > > >Michael "Murph" Robbert > > JJ -- Michael "Murph" Robbert System Administrator for Math/CS Colorado School of Mines, Golden, CO 80401-1887 Office: SH220 Office phone: 303-273-3786 Pager: 303-461-6543 or Text messages: [EMAIL PROTECTED] Email: [EMAIL PROTECTED]
