NSLU2-Linux
view · edit · print · history

HowTo.FreeMoreMemory History

Hide minor edits - Show changes to markup

June 10, 2009, at 11:44 AM by Neil Ronketti --
Changed line 77 from:

It is worth mentioning that the WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

to:

It is worth mentioning that the watchdog script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

June 10, 2009, at 11:44 AM by Neil Ronketti --
Changed line 77 from:

It is worth mentioning that the /usr/sbin/WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

to:

It is worth mentioning that the WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

June 10, 2009, at 11:35 AM by Neil Ronketti --
Changed line 77 from:

It is worth mentioning that the /usr/sbin/WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

to:

It is worth mentioning that the /usr/sbin/WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

June 10, 2009, at 11:33 AM by Neil Ronketti -- Added details of crontab restarting thttpd
Changed lines 75-77 from:

@]

to:

@]

It is worth mentioning that the /usr/sbin/WatchDog? script will restart the thttpd process on a regular basis if it is being called from crond, as is the default behaviour. This is documented in the BootSequencePage

January 05, 2009, at 06:58 PM by Michael --
Added lines 45-46:

~when I did this, it also disabled my telnet access, leaving me unable to log in and undo this change!

Changed lines 51-52 from:

Create a called rc.samba at /unslung with these two lines:

to:

Create a diversion script called rc.samba at /unslung with these two lines:

September 02, 2008, at 12:21 PM by fcarolo -- updated info and formatting
Changed lines 3-4 from:

Disable UPnP

to:

Disable UPnP

Changed lines 9-10 from:

Disable support for Maxtor OneTouch USB drives

to:

Disable support for Maxtor OneTouch USB drives

Changed lines 30-31 from:

Disable xinetd and FTP support

to:

Disable xinetd and FTP support

Changed lines 38-39 from:

To prevent it from starting at next boot, create a file called /unslung/rc.xinetd with:

to:

To prevent it from starting at next boot, create a diversion script called /unslung/rc.xinetd with:

Changed lines 45-73 from:

by Fcarolo, September 2009

to:

Disable Samba

If you have other uses for your slug and do not need the built-in Samba server, you can disable it using some diversion scripts.

Create a called rc.samba at /unslung with these two lines:

#!/bin/sh
return 0

Since you are not running Samba, you can also divert other scripts used for maintenance tasks related to it. Create two extra scripts at /unslung, with the same content as rc.samba, called rc.quota and rc.reset_usrgrpshare. This will also make the slug boot a little faster.

After creating these scripts, reboot the slug through the web interface or using the DO_Reboot script.

Disable the Built-in Web Server

You can disable the built-in web server if you comfortable with managing the slug using only a command line shell.

To stop the web server:

killall thttpd

To prevent it from starting at next boot, create a diversion script called /unslung/rc.thttpd with:

#!/bin/sh
return 0
September 01, 2008, at 07:53 PM by fcarolo -- updated info and formatting
Changed line 45 from:

by Profiles/Fcarolo, September 2009

to:

by Fcarolo, September 2009

September 01, 2008, at 07:53 PM by fcarolo -- typo
Changed lines 38-39 from:

To prevent it from starting at next boot, create a file called /unslung/rc.xinted with:

to:

To prevent it from starting at next boot, create a file called /unslung/rc.xinetd with:

Changed line 45 from:

by Profiles/fcarolo, September 2009

to:

by Profiles/Fcarolo, September 2009

September 01, 2008, at 07:52 PM by fcarolo -- updated info and formatting
Changed lines 9-10 from:

Disable support for Maxtor OneTouch? USB drives

to:

Disable support for Maxtor OneTouch USB drives

September 01, 2008, at 07:52 PM by fcarolo -- updated info and formatting
Deleted line 20:
Deleted line 22:
Deleted line 41:
Added lines 44-45:

by Profiles/fcarolo, September 2009

September 01, 2008, at 07:51 PM by fcarolo -- updated info and formatting
Changed lines 1-5 from:

Tip to increase available user RAM slightly

You can also free up a small amount of user RAM for use by other packages by disabling the UPNP functionality using the Web configuration pages.

RobHam June 2005


to:

These are some tips to increase available memory under Unslung 6.x.

Disable UPnP

You can free up a small amount of RAM for use by other packages by disabling the UPnP functionality using the web configuration pages. Go to the Administration section for the web interface, and under the System tab, uncheck Enable UPnP Support.

by RobHam, June 2005

Disable support for Maxtor OneTouch? USB drives

Changed lines 17-26 from:

You can permanently disable onetouch_detect by editing the file /etc/rc.d/rc.quickset. You need to be root to do this. Edit the file and comment out the line:

/usr/sbin/onetouch_detect; check_status

slebetman-August 2005

to:

To make this change permanent, but also easy to revert, create a diversion script for rc.quickset. In the /unslung directory, create a file called rc.quickset containing these lines:

#!/bin/sh

/usr/sbin/QuickSet; check_status
/usr/sbin/USB_Detect; check_status

return 0

This script will run the original commands from /etc/rc.d/rc.quickset, except for the onetouch_detect utility.

by slebetman, August 2005

Disable xinetd and FTP support

If you do not use the built-in FTP server available from Unslung (actually, the original FTP server by Linksys) you can stop xinetd and prevent it from starting.

To stop xinted, run

killall inetd

To prevent it from starting at next boot, create a file called /unslung/rc.xinted with:

#!/bin/sh

return 0
January 08, 2008, at 12:08 PM by fcarolo -- fixed false wikilink
Changed lines 6-7 from:

If, like me, you don't have Maxtor's OneTouch? drives you can also disable the built in onetouch software to free even more ram.

to:

If, like me, you don't have Maxtor's OneTouch drives you can also disable the built in onetouch software to free even more ram.

December 25, 2007, at 12:50 AM by betonpolatie -- removed untrue content
Deleted lines 21-32:

smbd (or Samba Deamon) seems to occupy a lot of memory resources. If you, like me do not need samba shares, simply disable samba by means of DiversionScript? In the /unslung directory, add a file 'rc.samba' with contents:

#!/bin/sh
return 0

Now I have made this file executable using 'chmod +x rc.samba', I do not know if that is needed; but it works like a charm.

In original state; about 700 to 1000 1k blocks free; now approximately 6700 1k blocks free.

Betonpoaltie - oct '07

October 17, 2007, at 02:09 PM by betonpoaltie --
Changed lines 25-27 from:
@@#!/bin/sh
@@return 0
to:
#!/bin/sh
return 0
October 17, 2007, at 02:08 PM by betonpoaltie --
Changed lines 25-27 from:
  1. !/bin/sh

return 0

to:
@@#!/bin/sh
@@return 0
October 17, 2007, at 02:08 PM by betonpoaltie --
Changed line 22 from:

---

to:

October 17, 2007, at 02:07 PM by betonpoaltie -- disable samba
Changed lines 20-32 from:

slebetman-August 2005

to:

slebetman-August 2005

--- smbd (or Samba Deamon) seems to occupy a lot of memory resources. If you, like me do not need samba shares, simply disable samba by means of DiversionScript? In the /unslung directory, add a file 'rc.samba' with contents:

  1. !/bin/sh

return 0

Now I have made this file executable using 'chmod +x rc.samba', I do not know if that is needed; but it works like a charm.

In original state; about 700 to 1000 1k blocks free; now approximately 6700 1k blocks free.

Betonpoaltie - oct '07

November 24, 2006, at 08:45 PM by mrkzander --
Changed lines 10-12 from:
killall /usr/sbin/onetouch_detect
to:
killall onetouch_detect
August 26, 2005, at 04:33 AM by slebetman --
Changed line 14 from:

""/etc/rc.d/rc.quickset"". You need to be root to do this.

to:

/etc/rc.d/rc.quickset. You need to be root to do this.

August 26, 2005, at 04:32 AM by slebetman --
Changed line 14 from:

/etc/rc.d/rc.quickset file. You need to be root to do this.

to:

""/etc/rc.d/rc.quickset"". You need to be root to do this.

August 26, 2005, at 04:30 AM by slebetman --
Changed line 5 from:
to:

Changed lines 8-12 from:

You can kill the onetouch_detect software by issuing: killall /usr/sbin/onetouch_detect

to:

You can kill the onetouch_detect software by issuing the command:

killall /usr/sbin/onetouch_detect
Changed lines 14-19 from:

/etc/rc.d/rc.quickset and commenting out the line: /usr/sbin/onetouch_detect; check_status you need to be root to do this.

to:

/etc/rc.d/rc.quickset file. You need to be root to do this. Edit the file and comment out the line:

/usr/sbin/onetouch_detect; check_status
August 26, 2005, at 04:25 AM by slebetman --
Changed lines 9-12 from:

@@ killall /usr/sbin/onetouch_detect @@

to:

killall /usr/sbin/onetouch_detect

Changed lines 15-17 from:

@@ /usr/sbin/onetouch_detect; check_status @@

to:

/usr/sbin/onetouch_detect; check_status

August 26, 2005, at 04:24 AM by slebetman --
Added lines 5-20:

If, like me, you don't have Maxtor's OneTouch? drives you can also disable the built in onetouch software to free even more ram.

You can kill the onetouch_detect software by issuing: @@ killall /usr/sbin/onetouch_detect @@

You can permanently disable onetouch_detect by editing the file /etc/rc.d/rc.quickset and commenting out the line: @@ /usr/sbin/onetouch_detect; check_status @@ you need to be root to do this.

slebetman-August 2005

June 22, 2005, at 03:10 PM by tman -- Moved from ModifyMemorySize
Added lines 1-4:

Tip to increase available user RAM slightly

You can also free up a small amount of user RAM for use by other packages by disabling the UPNP functionality using the Web configuration pages.

RobHam June 2005

view · edit · print · history · Last edited by Neil Ronketti.
Based on work by Neil Ronketti, Michael, fcarolo, betonpolatie, betonpoaltie, mrkzander, and slebetman.
Originally by tman.
Page last modified on June 10, 2009, at 11:44 AM