DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2008-05-29 23:09:15

steveG
Member
Registered: 2008-04-20
Posts: 15

/tmp in funplug 0.5

I notice that funplug is creating a /ffp/tmp directory, but I haven't noticed it being used.  I found that I was running out of space on /tmp with a perl script and fixed the problem by removing /tmp and replacing it with a symbolic link to /ffp/tmp.

Is there a reason that this isn't being done in the funplug script?

Offline

 

#2 2008-05-29 23:49:20

KRH
Member
From: Denmark
Registered: 2006-10-27
Posts: 219
Website

Re: /tmp in funplug 0.5

/tmp is used by the firmware to put some "importen" files.


First user to fun_plug the dns-323.

Offline

 

#3 2008-05-30 13:19:16

KyleK
Member
From: Dresden, Germany
Registered: 2007-12-05
Posts: 1178

Re: /tmp in funplug 0.5

I'd leave the original /tmp as it is, but point environment variables TMPDIR, TEMP and TMP to /ffp/tmp.
I also use the latter for lighthttpd (server.upload-dirs = ( "/ffp/tmp" ) in lighttpd.conf)

Out of curiosity, how did you run out of space in the original tmp dir?

Offline

 

#4 2008-05-30 14:19:20

fonz
Member / Developer
From: Berlin
Registered: 2007-02-06
Posts: 1716
Website

Re: /tmp in funplug 0.5

KyleK wrote:

Out of curiosity, how did you run out of space in the original tmp dir?

patch can use up quite a bit in /tmp (I've had quite a few 'disk full' errors from patch). gcc, gas, etc also default to /tmp if TMPDIR is not set.

Offline

 

#5 2008-05-30 23:12:47

steveG
Member
Registered: 2008-04-20
Posts: 15

Re: /tmp in funplug 0.5

KRH wrote:

/tmp is used by the firmware to put some "importen" files.

This is true; but I copied the existing contents to /tmp to /ffp/tmp before deleting the old /tmp and creating the symlink.  Unless the system changes the contents of the files in the brief time that it takes to copy the files and create the symlink, I don't see the problem.

Offline

 

#6 2008-05-30 23:17:32

SilentException
Member
From: Island of Krk, Croatia
Registered: 2008-05-04
Posts: 148

Re: /tmp in funplug 0.5

one problem (atleast for me) would be: unless you use usb for funplug and other stuff, this will just keep your disks up all the time..

but i would also use TMPDIR environment variable instead of linking. makes things look less "dirty" smile


D-Link DNS-323 v1.05 fun_plug-ed + many mods,  2 x 320GB Seagate Barracuda 7200.10 RAID0, Cat6 Gigabit Network, 9k Jumbo Frames, Average (WRITE): 19,32 MB/sec, Average (READ): 28,6 MB/sec

Offline

 

#7 2008-05-30 23:20:59

steveG
Member
Registered: 2008-04-20
Posts: 15

Re: /tmp in funplug 0.5

KyleK wrote:

I'd leave the original /tmp as it is, but point environment variables TMPDIR, TEMP and TMP to /ffp/tmp.
I also use the latter for lighthttpd (server.upload-dirs = ( "/ffp/tmp" ) in lighttpd.conf)

Out of curiosity, how did you run out of space in the original tmp dir?

Thanks.  I will try this.

I ran into the problem when I was trying to run the nzbperl script.  This script uses uudeview to decode the files that it downloads.  uudeview does the decode operation in /tmp before copying the result to the final location. 

For what it's worth, I am moving away from this solution for the moment due to the difficulty of daemonizing a perl process across logins and am trying to get nzbget compiled and running.

Offline

 

#8 2010-04-17 23:44:26

Whistle Master
Member
Registered: 2010-01-21
Posts: 15

Re: /tmp in funplug 0.5

KyleK wrote:

I'd leave the original /tmp as it is, but point environment variables TMPDIR, TEMP and TMP to /ffp/tmp.

I would like to change TMPDIR, TEMP and TMP variables. Where can I put the export command so that the variables are set at each reboot for the whole system ?

Thank you for your help !

EDIT: I'm answering myself, the export command has to be put in /etc/profile
:-)

Last edited by Whistle Master (2010-04-21 17:04:52)

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB