# swapon -s
Filename Type Size Used Priority
/dev/sda1 partition 241880 0 -1
I'm using a swap partition (not a file)and it is automatically mounted using one of my optware scripts (/opt/etc/init.d/S10swap) _________________ Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge
I just realized what "might" be your problem is with this above command. You must use the "direct" partition as the argument and it does not need to be mounted. From what I see though, you are using the file version of the program and that requires a special syntax I do believe. Here is the output of the usage:
Usage:
Code:
swapon -a [-e] [-v] [-f] enable all swaps from /etc/fstab
swapon [-p priority] [-v] [-f] <special> enable given swap
swapon -s display swap usage summary
swapon -h display help
swapon -V display version
The <special> parameter:
{-L label | LABEL=label} LABEL of device to be used
{-U uuid | UUID=uuid} UUID of device to be used
<device> name of device to be used
<file> name of file to be used
I do believe that you are trying to use the version from the second line. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
-i first try with V24SP1 then SP2 13064 (because it is for production network....No beta allowed)
Not a solution to your problem, I'm only curious of how you have managed to choose the 2 worst builds ever for Broadcom based devices. For a production network.. _________________ Kernel panic: Aiee, killing interrupt handler!
-i first try with V24SP1 then SP2 13064 (because it is for production network....No beta allowed)
Not a solution to your problem, I'm only curious of how you have managed to choose the 2 worst builds ever for Broadcom based devices. For a production network..
Simply because when you make production network you do not have time to be gambler with beta release. So you manage with what dev's consider as stable release.
you cannot swap directly on a network filesystem file because it's not a continous blockdevice. what the wiki ( http://www.dd-wrt.com/wiki/index.php/Linux_SWAP ) says with the loop device around the swap file is a work around this security measure.
Joined: 05 Dec 2009 Posts: 377 Location: Toronto, Canada
Posted: Mon May 17, 2010 21:06 Post subject:
yzy-oui-fi wrote:
LOM wrote:
yzy-oui-fi wrote:
-i first try with V24SP1 then SP2 13064 (because it is for production network....No beta allowed)
Not a solution to your problem, I'm only curious of how you have managed to choose the 2 worst builds ever for Broadcom based devices. For a production network..
Simply because when you make production network you do not have time to be gambler with beta release. So you manage with what dev's consider as stable release.
I play with beta at home but never for my customers network. It is very different to play on a network which own 10 clients and another which should be able to own 5 or 10 time more. There could be some very bothering issue with beta on prodution network, and i don't want to drive 500 km in a middle of a night for a network break down, spend two or three days on site without giving a solution just because it is a bug issue of a beta release...Am I clear enough?
I wouldn't use beta builds in production either but I would NEVER deploy SP1 or 13064 in any production environment, considering all the known problems 13064 has.
Ok so could you tell me which stable release you use for production network if you do not use SP1 or SP2(13064) which are the one recommanded to be more stable by dd-wrt website? V23sp2? ;)
ReadtheAnnouncements! wrote:
So...put on a build that you should KNOW won't work?
You are right that it isn't a gamble...more of a sure thing that there will be major problems.
the only real problem is the fact swap file could not be load.
Maybe this will seem incredible for lot of people here but i have wiman network covering 25km² support by dd-wrtv24sp1 rebuilt(to included my network setup as default parameters) running for 3 years without problems. So i think the bugs related to SP1 is not bothering in wds mesh network with chillispot running on gateway. the only thing bothering is that the gateway is wrt54GS 1.1 to enable the ssl captiv portal without overloading the memory.
