I tried: `which detachtty` --dribble-file foo.dribble \<br>
--log-file foo.log \<br>
--pid-file foo.pid \<br>
foo.socket /usr/bin/sbcl<br>
then: attachtty foo.socket<br>
and I get the sbcl prompt. So detachtty/attachtty by themselves seem to work.<br><br><div><span class="gmail_quote">On 4/12/06, <b class="gmail_sendername">Marco Baringer</b> <<a href="mailto:mb@bese.it">mb@bese.it</a>
> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"Daniel Patru" <<a href="mailto:dpatru@gmail.com">dpatru@gmail.com
</a>> writes:<br><br>> UCW doesn't start on my machine when used with detachtty. However it starts<br>> without it. In ucwctl, the start option says:<br>><br>> start)<br>> install -d -m 755 $LOGROOT $RUNROOT
<br>> $DETACHTTY --dribble-file $LOGROOT/ucw.dribble \<br>> --log-file $LOGROOT/ucw.detachtty \<br>> --pid-file $RUNROOT/ucw.pid \<br>> $RUNROOT/ucw.socket \<br>>
$CLLAUNCH -X $OPT_LISP $OPT_PATH NO_QUIT=yes -- "$STARTFILE"<br>> ;;<br><br>colud you try just running lisp, through detachtty, from the console?<br>(i'd like to know if the issue is detachtty itself or how we're
<br>calling detachtty). try osmething like this:<br><br>`which detachtty` --dribble-file foo.dribble \<br> --log-file foo.log \<br> --pid-file foo.pid \<br> foo.socket sbcl
<br><br>(assuming you're using sbcl)<br><br>--<br>-Marco<br>Ring the bells that still can ring.<br>Forget the perfect offering.<br>There is a crack in everything.<br>That's how the light gets in.<br> -Leonard Cohen
<br><br>_______________________________________________<br>bese-devel mailing list<br><a href="mailto:bese-devel@common-lisp.net">bese-devel@common-lisp.net</a><br><a href="http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel">
http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>"Work and play are used to describe the same thing under differing circumstance."<br> - Mark Twain