IPCOP is a firewall distro that runs fairly well

Someone who uses it can document this more. AddToMe

This is from Nick Rout (nick at rout dot co dot nz) when he ran out of Inodes on /var on his ipcop? box. Nick is active in CLUG.

Subject: HELP! How do I make more inodes
Date: 09 Sep 2003 11:53:35 +1200

For the record I did the following:

0. from the backup box SCP the rsync(1) 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.

IsomerMadeMeDoThis