version 0.1.25-rc2 initrd suggestion

Issue #328 resolved
merlin81 created an issue

pilerconf uses hardcoded conf file path. as pilerconf is used in init scripts, maybe it would be better to use a variable to add conf file. example: /etc/default/piler: pilerconf_opts="-c /PATH/TO/CONF" piler_opts="-c /PATH/TO/CONF"

and in /etc/init.d/rc.piler: . /etc/default/piler PID_FILE=/usr/sbin/pilerconf $pilerconf_opts -q pidfile | cut -f2 -d=

and

start() { echo "starting $NAME . . ." /usr/sbin/piler -d $piler_opts }

Comments (2)

  1. Janos SUTO repo owner

    Well, the config path is not hardcoded in pilerconf, instead it uses a default value (comes from --sysconfdir at configure time), however it can be overridden using -c. Anyway I've added an OPTION variable to rc.piler.in, so you may adjust paths in the init script. Btw. I don't think it's initrd related :-)

  2. Log in to comment