PKGBUILD and daemon start script question.

cactus · 2005-04-30 22:04:17

I am wondering about what the appropriate resolution to the following issue is. I have a temporary solution, but I am not sure if it is appropriate.

Here is the problem.

The lighttpd daemon can compress files for delivery (think apache mod_deflate). A temp directory needs to be specified, so the compressed file can be stored there for quick redelivery. This is held in the 'compress.cache' variable in the lighttpd.conf file.

The problem is, I wanted to specify a subdirectory of the tmp dir, "/tmp/lighttpd/cache". This directory is not created by the daemon itself, and must be preexisting, or an error is produced. Upon server reboot, the contents of /tmp is wiped.

I have temporarily added the following to the "start" stanza of my /etc/rc.d/lighttpd file:

DAEMON_CONF="/etc/lighttpd/lighttpd.conf"
COMPRESS_DIR=`cat ${DAEMON_CONF} | grep -e "^compress.cache" | grep -oe "/.*/"`

_*snip*_

if [ ! -z "$COMPRESS_DIR" ] && [ ! -d "$COMPRESS_DIR" ]; then
  mkdir -p -m777 $COMPRESS_DIR
fi

The above works, and creates the dir if it does not exit. My question is, is this an appropriate and correct solution? Would it be better to adjust the daemon to use the top level /tmp directory?

Xentac · 2005-04-30 22:24:19

I would leave it the way it is. An init script can do certain initialization things before it starts the daemon, like the mysql script does. Just as long as those things aren't things that should be done inside the package and won't break if done repeatedly (yours won't be executed repeatedly because of the if statement).

cactus · 2005-04-30 22:50:46

So, by leave it the way it is, I assume you mean the change I made was warrented?

phrakture · 2005-05-01 01:02:35

I wouldn't auto create the dir - it'll fail with some message saying "compress module can't find cache dir" or something to that effect

cactus · 2005-05-01 01:22:28

yes, but the point is every reboot it will say it. A side effect of /tmp being erased on every boot. In theory, the daemon itself should "try" to create the directory if it does not exist..But since the daemon does not, I would think it is a reasonable solution.

I am still not positive though. One for and one against so far..

swiergot · 2005-05-01 07:40:06

I would let the init script create the directory. Another way is to use a directory under /var/cache.

cactus · 2005-05-01 07:46:53

hmmmm. /var/cache. I didn't even think about that. Would it be better to put something temporary like a gzip html file cache into /var/cache, or into /tmp?

EDIT: I decided to just add a directory to the /home/lighttpd dir, and call it cache. It was either that of /var/cache/lighttpd. If anyone has a preference or thinks one location is better than another, let me know..
I also moved php-eaccelerator's cache dir to /var/cache/eaccelerator

phrakture · 2005-05-01 17:02:03

yeah, mine is running with the cache dir next to the "pages" and "log" dir - yeah it's not using tmp... but I don't care...

i3839 · 2005-05-01 17:44:32

Better not to use /tmp, but /var or something else instead. A lot of security holes come from unsafe file handling in /tmp.

Arch Linux

#1 2005-04-30 22:04:17

PKGBUILD and daemon start script question.

#2 2005-04-30 22:24:19

Re: PKGBUILD and daemon start script question.

#3 2005-04-30 22:50:46

Re: PKGBUILD and daemon start script question.

#4 2005-05-01 01:02:35

Re: PKGBUILD and daemon start script question.

#5 2005-05-01 01:22:28

Re: PKGBUILD and daemon start script question.

#6 2005-05-01 07:40:06

Re: PKGBUILD and daemon start script question.

#7 2005-05-01 07:46:53

Re: PKGBUILD and daemon start script question.

#8 2005-05-01 17:02:03

Re: PKGBUILD and daemon start script question.

#9 2005-05-01 17:44:32

Re: PKGBUILD and daemon start script question.

Board footer