• Registered: 2010-09-11
  • Posts: 2

Topic: Feedback from init.d scripts and/or fuppes 0.675

Howdy all,
    I'm new to Crunchbang and am still learning the ropes, so be gentle smile.
I have been trying to set up the fuppes (0.675) media server on my Crunchbang installation for the past week and have hit a wall. A week's worth of googling and searching through the Ubuntu message boards have yet to produce an effective solution. The server runs great when I run it from the command line, but not when called from my init.d script, which was set up following the directions found here: http://fuppes.ulrich-voelkel.de/wiki/in … ith_Init.d . I believe the script is running since it logged a few echos I put in it (ie echo sometext >> somelog), leading me to suspect that fuppes may be failing. Unfortunately, this seems to be all the information I can get to; I can figure out how to capture the log_daemon_msgs on boot, and every time I try to pass a log file to fuppes (/var/log/fuppes.log) with either --log-file or -m, I get a "not recognized as a valid path" or some such nonsense.

Has anyone run into this issue before? How can I capture the log_daemon_msgs? Any other suggestions about where to look next?

Thanks for any help you all can provide.

  • Registered: 2010-09-11
  • Posts: 2

Re: Feedback from init.d scripts and/or fuppes 0.675

Quick update-
    Plugged a monitor into my Crunchbang rig (It was running headless), removed the quiet and splash flags from my grub menu.lst, and disabled the gdm startup to watch the log_daemon_msgs as they came in. Everything looked fine. Played with htop for a while and tried again, and everything seemed to be starting up properly. Not sure what I did.

I would still like to know if there is a way to capture the boot console output if I'm booting remotely. Any suggestions?

Thanks.