[Voyage-linux] Shorewall Read Only /var/lib/shorewall/ problem
Kim-man 'Punky' Tse
(spam-protected)
Wed Mar 12 21:12:53 HKT 2008
Hi all,
There was some discussion. I was now thinking to use unionfs/aufs to
hold all modified files to a copy-on-write (/cow) directory, then have a
manally script that sync cow back to flash disk. Is it possible and are
there any recipe for this?
Regards,
Punky
Wayne Lee wrote:
>
> Chris
>
>
>
> I also noticed when using shorewall it did slow down the throughput of
> the data.
>
>
>
> I can get double the amount without shorewall, the test was done on a
> old version of shorewall and voyage and I have not retested recently.
>
>
>
>
>
>
>
>
>
>
>
> *From:* voyage-linux-bounces+wayne.lee=link-connect.com at list.voyage.hk
> [mailto:voyage-linux-bounces+wayne.lee=link-connect.com at list.voyage.hk]
> *On Behalf Of *Chris Morley
> *Sent:* 12 March 2008 12:50
> *To:* voyage-linux at voyage.hk
> *Subject:* [Voyage-linux] Shorewall Read Only /var/lib/shorewall/ problem
>
>
>
> Hi,
>
> I am trying to get shorewall running and whilst it installs from
> apt-get fine, i am having issues with the Read only file system.
> Shorewall seems to write the compiled scripts into /var/lib/shorewall.
> When i run remountrw there is no problem, however with remountro
> hitting 'shorewall start' in the shell gives a whole raft of errors:
>
> Compiling...
> /usr/share/shorewall/functions: line 1704:
> /var/lib/shorewall/.modulesdir: Read-only file system
> cp: cannot remove `/var/lib/shorewall/.modules': Read-only file system
>
> [..snip..]
>
> /var/lib/shorewall/.start: line 1046: /var/lib/shorewall/chains:
> Read-only file system
> /var/lib/shorewall/.start: line 1048: /var/lib/shorewall/nat:
> Read-only file system
> /var/lib/shorewall/.start: line 1050: /var/lib/shorewall/proxyarp:
> Read-only file system
> /var/lib/shorewall/.start: line 1052: /var/lib/shorewall/zones:
> Read-only file system
> /var/lib/shorewall/.start: line 1065: /var/lib/shorewall/restarted:
> Read-only file system
> Processing /etc/shorewall/start ...
> /usr/share/shorewall/functions: line 2368: /var/lib/shorewall/state:
> Read-only file system
> Processing /etc/shorewall/started ...
> cp: cannot remove `/var/lib/shorewall/.restore': Read-only file system
> done.
>
> Is there any way that this /var/lib/shorewall/ directory can be made
> rw? Or perhaps even plain old ramdisk is ok, but consist of a default
> set of files upon boot? Would appreciate insights if the two options
> above are possible.
>
> The other option is for me to change the init.d/shorewall scripts to
> remountrw and remountro around the start and stop parts, but i would
> prefer the solution above and it would also help me learn about voyage
> linux which rocks :)
>
> Many thanks in advance,
>
> Chris
>
> ------------------------------------------------------------------------
>
> Everything in one place. All new Windows Live!
> <http://www.windowslive.co.uk/get-live>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Voyage-linux mailing list
> Voyage-linux at list.voyage.hk
> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
More information about the Voyage-linux
mailing list