Re: Executed programs appending to syslog.

From: Peter Ajamian (
Date: 03/09/01

"Shane P. Lee" wrote:
> > Why do you want to run it nohup anyways?  It has nothing to do with
> > where the output of the program goes.
> I didn't know that. I don't know a lot of things, actually :P

In that case you'll probably not want to run it with nohup.  Without
nohup the bot _might_ die when the mud shuts down (crashes, reboots,
etc).  With nohup, it definately won't unless you provide it some other
means of determining when to die off (does it die when it looses the
connection to the MUD?).  You'll need to take that into consideration
because you ceartainly won't want to leave the bot running after the MUD
dies off.

> j/k, it's a small tintin bot that connects to the MUD. After I get
> a Mass/Neotek robot re-written to CircleMUD, I plan to use the code
> to activate it instead. If you can think of a "better" way of doing
> this, please let me know.
> I didn't include the program info because I only wanted comments about
> the code, not the bot. Now I'll accept comments about the bot:P

I was interested because I was wondering about the the \r's you were
getting (^M is another way of expressing \r, they both refer to a
carriage-return character).  It would appear that the output you're
getting comes directly off the MUD which does send the DOS/Windows style
\r\n at the end of a line instead of the Unix style \n.  This is to
conform with the TELNET standard.  What's strange about it is that TINTIN
should be translating that back to the Unix standard \n before sending it
to the screen, oh well *shrugs*.

Regards, Peter

   | FAQ: |
   | Archives: |

This archive was generated by hypermail 2b30 : 12/04/01 PST