[Bese-devel] ./bin/ucwctl suggestions

[Nathan Bird]

I hadn't really used ucwctl much, when I tried it today with sbcl every time
I tried to slime-connect (over ssh tunnel) lisp would exit right after/as it
connected.  Anybody else seen this behavior

But having looked at ucwctl to see what was going on there it seems that the
code there is a bit more succinct than start.lisp so I changed start.lisp to
use this style (create-server). I believe this is what Robert Marlow
introduced at the beginning of August that was never moved into start.lisp.

Another reason was because I have been trying several of the different
backends today and it was bugging me that they were on different ports.

I believe all of the necessary setup is being done here. So far though I
have only written (half of) one UCW app, then also trying to make sure that
admin and examples are still working. There might be stuff about working
with several at once that I have not yet grokked.


I removed the warning comment while making the araneida backend against
using the default-url accessor, as it seemed to be incorrect.

*ucw-tal-root* was listed in the export of packages.lisp twice.


Nathan Bird

-----Original Message-----
From: bese-devel-bounces at common-lisp.net
[mailto:bese-devel-bounces at common-lisp.net] On Behalf Of Marco Baringer
Sent: Thursday, September 08, 2005 1:57 PM
To: Craig McDaniel
Cc: bese-devel at common-lisp.net
Subject: Re: [Bese-devel] ./bin/ucwctl suggestions

Craig McDaniel <craigmcd at gmail.com> writes:

> Suggested changes to ./bin/ucwctl (Darcs patch included)
>
>
> 1. CMUCL uses "-eval" instead of "--eval" for command line
>    argument. Change the ucwctl script to use more flexible $EVAL
>    variable.

would it be worth the offort to use fare's lisp.sh (or whatever it's
called) script generator? that apperas to support quite a large number
of differente lisps.

> 2. When calling "ucwctl stop", attachtty only accepts one argument, the
>    remote socket. It doesn't know what to do with the "eval" commands
>    passed in. Replaced with echo and pipe commads to provide graceful
>    shutdown. Keep the "kill -s QUIT" command available as "stop2" in
>    case the graceful method doesn't work.

i've a modified version of attachtty which accepts both the eval and a
timeout argument. what's the canonical location for detachtty? who
develops it? is there some 'official' web page i can look to and see
what options people can be expected to have?

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen
_______________________________________________
bese-devel mailing list
bese-devel at common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: start.lisp.darcs
Type: application/octet-stream
Size: 21373 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050908/c1b78028/attachment.obj>