automated starting aborts with MSG534

[d]

Hi.

I configure'd, make'd, make install'd eggdrop as normal (non-root) user into a
subdirectory of ~. I can run the program manually without problems by changing
into that dir, then invoking the executable conffile.

However I wish to automate that and run it along with my other services during
system boot. Excerpt from /etc/init.d/boot.local:

/usr/local/apache2/bin/apachectl restart
/usr/local/sbin/proftpd
/usr/bin/timidity -iA -B2,8 -Os & >/dev/null
/sbin/kbdrate -r 30 -d 150
su -c "/home/user/bin/eggd/eggdrop /home/user/bin/eggd/conffile" user

This is where I get the following talkback:

[14:58] --- Loading eggdrop v1.6.10 (Sat Jun 15 2002)
[13:58] MSG20B dns: //modules/dns.so: cannot open shared object file: No such file or directory
[13:58] MSG20B channels: //modules/channels.so: cannot open shared object file: No such file or directory
[13:58] Tcl error in file '/home/user/bin/eggd/conffile':
[13:58] invalid command name "channel"
while executing
"channel add #foobar {
idle-kick 0
}"
(file "/home/user/bin/eggd/conffile" line 69)
[13:58] * MSG534

Obviously, eggy doesn't seem to find its modules. I request the feature that
future versions of eggdrop can be started from anywhere, like it can be done
with the other services. Meanwhile, is there a quick
workaround for my situation?

[Petersen]

yes, stop using relative paths in your conf and use full paths instead

[Petersen]

or su -c "cd /home/user/bin/eggd && ./eggdrop confile"

[d]

D'oh. Yes, changing the directory beforehand avoids the problem.

/me = braindead.

Thanks.