So I've been having problems getting the Fuppes daemon to startup at powerup. I followed the directions for Debian verbatim off the Wiki, but it's never powered up when I look for the process after it finishes booting. I doubled checked that the user fuppes is properly created and everything is owned by that user. Also checked to make sure the fuppesd script is executable by everyone and verified that all the sym links exist in all the rcx.d directories. I'm somewhat at a loss as to why it isn't starting up on its own. When I run /etc/init.d/fuppesd start manually it works perfectly.
Any ideas would be greatly appreciated.
try this link instead: http://fuppes.ulrich-voelkel.de/wiki/index.php/Compiling_on_Ubuntu_Linux
I used that on my ubuntu 7.10 server and it worked perfectly... right up to the latest svn-591.
I should have said use that link to compile and then the init.d link to get fuppesd to autoload :)
Strangely enough, I am now having the same problem when the init rc.d script which was previously working fine.
Pls set the log level on the fuppesd file to 3 and see what the log file says. The error message that i have on mine is failure to bind to socket. I've tried changing to different port numbers but that does not appear to resolve the problem. I am also able to use fuppes by manual starting this via /etc/init.d/fuppes start.
I am wondering if this has to do with AppArmor or is there a bug with the httpd?
frizz: I actually used both of those links to compile and setup the init.d. That's why I'm so curious is to why it's not loading on powerup. Any ideas of how to debug and figure out why it's not getting run at init?
Unfortunately no. Compiling fuppes is about as technical as I've ever gotten with linx :)
99% of my IT knowledge is on the various flavours of Windows.