Re: daemondo / launchd just being silly on me

2009-11-10 Thread dreamcat four
Hello again, The root of my problem: On Sun, Nov 8, 2009 at 7:39 PM, dreamcat four dreamc...@gmail.com wrote: startupitem.executable  ${prefix}/lib/ruby/gems/1.8/bin/stompserver --working_dir /var which creates the attached plist file. But for the life of me it just won't start. It turns

Re: daemondo / launchd just being silly on me

2009-11-10 Thread dreamcat four
Created Ticket #22449 http://trac.macports.org/ticket/22449 Hmm, maybe its worth to file a bug report just to improve the documentation slightly. dreamcat4 dreamc...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org

Re: daemondo / launchd just being silly on me

2009-11-09 Thread dreamcat four
On Mon, Nov 9, 2009 at 1:51 AM, Scott Haneda talkli...@newgeo.com wrote: I do not know anything about stompserver.  How I would debug this... Can you start the server by hand, on the command line?  If so, sounds like you are doing pretty good.  Are you sure that --working_dir=/var is correct?

Re: daemondo / launchd just being silly on me

2009-11-09 Thread Scott Haneda
You are a bit more advanced in your knowledge of C and other related code, sorry I was not more help, comments interspersed below... On Nov 9, 2009, at 4:09 AM, dreamcat four wrote: On Mon, Nov 9, 2009 at 1:51 AM, Scott Haneda talkli...@newgeo.com wrote: I do not know anything about

Re: daemondo / launchd just being silly on me

2009-11-08 Thread dreamcat four
Well, Heres the launchd log with debugging switched on. dreamcat4 dreamc...@gmail.com stompserver-launchd-debug.log Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org

Re: daemondo / launchd just being silly on me

2009-11-08 Thread Scott Haneda
I do not know anything about stompserver. How I would debug this... Can you start the server by hand, on the command line? If so, sounds like you are doing pretty good. Are you sure that --working_dir=/var is correct? My understanding is that path is a portfile violation, Then again,