Annotated edit history of
IPCop version 3, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
AristotlePagaltzis |
1 |
A FireWall-centric LinuxDistribution with a web-based configuration interface. |
| |
|
2 |
|
| |
|
3 |
!! How to fix the scarcity of [Inode]s on <tt>/var</tt> |
| |
|
4 |
|
| |
|
5 |
Since having <tt>/var/log</tt> mounted is not essential for continued running, this is easy as long as you have another machine to copy everything to. |
| |
|
6 |
|
| |
|
7 |
# rsync(1) is not included with [IPCop] by default, so [SCP] it from another machine: |
| |
|
8 |
<verbatim> |
| |
|
9 |
scp -P 222 /usr/bin/rsync ipcop:/usr/bin/rsync |
| |
|
10 |
</verbatim> |
| |
|
11 |
|
| |
|
12 |
# Make a temporary directory on the backup machine and change into it. |
| |
|
13 |
Make sure it's on a [Partition] with enough room. |
| |
|
14 |
|
| |
|
15 |
# On the backup machine: |
| |
|
16 |
<verbatim> |
| |
|
17 |
rsync -vaz -e 'ssh -p 222' ipcop:/var/log/\* . |
| |
|
18 |
</verbatim> |
| |
|
19 |
This recursively copies the directory contents, preserving file attributes, using compression. |
| |
|
20 |
The <tt>-e</tt> switch tells rsync(1) how to invoke ssh(1). |
| |
|
21 |
It is necessary because the [IPCop] [SSH] daemon runs on port 222. |
| |
|
22 |
|
| |
|
23 |
# Now on the [IPCop] machine, make a new file system with approx 4 times as many [Inode]s as before: |
| |
|
24 |
<verbatim> |
| |
|
25 |
umount /var/log |
| |
|
26 |
mke2fs -j -N 65536 /dev/harddisk3 |
| |
|
27 |
mount /var/log |
| |
|
28 |
</verbatim> |
| |
|
29 |
|
| |
|
30 |
# And now copy the whole thing back: |
| |
|
31 |
<verbatim> |
| |
|
32 |
rsync -avz -e 'ssh -p 222' . ipcop:/var/log |
| |
|
33 |
</verbatim> |
| |
|
34 |
|
| |
|
35 |
# Check that everything looks right on the [IPCop] machine and (for good measure) reboot it. |
| 2 |
AdrianKitto |
36 |
|
| 3 |
CraigBox |
37 |
----- |
| 2 |
AdrianKitto |
38 |
CategoryDistribution |
