beautiful for the record I did the following:
0. from the backup box scp the rsync binary to the ipcop box, as its not included there by default. must remember to remove it. first i checked which libraries it links to, which looked minimal so I figured it would work on ipcop. whereis rsync ldd /usr/bin/rsync scp -P 222 /usr/bin/rsync ipcop:/usr/bin/rsync 1. from the backup box, make a temp directory and cd into it, after making sure there was enough room on that partition for the data to be transferred. 2. from the backup machine: rsync avz -e "ssh -p 222" ipcop:/var/log/* . -a=archive (preserves file attributes and recurses thru directories) -v =verbose -z = compress to speed up over the network -e = use ssh instead of rsync to log into ipcop, ipcop runs ssh on port 222 and thats a dot (current dir) at the end wait for rsync to finish. 3. on ipcop umount /var/log mke2fs -j -N 65536 /dev/harddisk3 (make a new file system with approx 4 times as many inodes as before) mount /var/log 4 on backup machine rsync -avz -e "ssh -p222" . ipcop:/var/log wait again 5. check out everything looks right on ipcop and (for good measure) reboot it. Luckily having /var/log mounted is not essential for continued running. If i'd had to do this on / I would have needed to use a rescue disk, which would have meant attaching a monitor. keyboard etc. As it is I didn't go within 20 feet of the ipcop box. On Tue, 09 Sep 2003 10:40:51 +1200 Nick Rout <[EMAIL PROTECTED]> wrote: > there seems to be an awful lot in /log/snort > > I am currently rsyncing the entire /var filesystem to another box over > the lan. then i'll reformat /var/ and rsync it all back. > > and i'll make plenty of inodes > > Thanks to all for the qwuick help > > On Tue, 09 Sep 2003 10:16:59 +1200 > Christopher Sawtell <[EMAIL PROTECTED]> wrote: >
