Running an eggdrop from another eggdrop + Weird Crashing bug

[Weirdo]

Right, i have 2 bots on aniverse. both using windrop 1.6.13 (Which i discovered has a few issues with some of my scripts, think its a tcl lib thing, more stuff to do tonite ). Cause of the recent problems with the Routers on Aniverse's ISP, i have been disconnected form the network a lot. Now, this has crashed my channel admin bot, Minako completely.

I would like to make a script that would run the minako.exe from my other bot, which has so far, ridden out the worst of the netsplits . A sort of, Log onto Partyline in the other bot, do a .runminako command, and the tcl would exectue the minako executable. (Since i am converting my Windrop to Eggdrop in a couple of weeks when i get my linux box set up, something that could be mostly compatiable would kick ass )

If anyone could help me with the disconnection problems it would be wonderful. Its sort of random, trying to figure it out.

It happened twice so far today.

[05:46] Switching back to nick Minako
[05:46] Last message repeated 1 time(s).
[05:46] Regained nickname 'Minako'.
[05:50] @#cometanime (+ptnl 20) : [m/12 o/4 h/0 v/1 n/7 b/0 e/- I/-]
[05:50] @#weirdo (+pctn) : [m/2 o/2 h/0 v/0 n/0 b/0 e/- I/-]
[05:55] @#cometanime (+ptnl 20) : [m/12 o/4 h/0 v/1 n/7 b/0 e/- I/-]
[05:55] @#weirdo (+pctn) : [m/2 o/2 h/0 v/0 n/0 b/0 e/- I/-]
[06:00] @#cometanime (+ptnl 20) : [m/12 o/4 h/0 v/1 n/7 b/0 e/- I/-]
[06:00] @#weirdo (+pctn) : [m/2 o/2 h/0 v/0 n/0 b/0 e/- I/-]
[07:43] Identd: Listening On Port 113, Replying as Minako***
[07:43] Trying server irc-4.aniverse.com:6667
[07:43] Connected to irc-4.aniverse.com
[07:43] -NOTICE- *** Looking up your hostname...

It died just after 6am, and came back at 07:43 when i rebooted her

[09:37] Disconnected from irc-4.aniverse.com
[09:37] Identd: Listening On Port 113, Replying as Minako***
[09:37] Trying server irc.aniverse.com:6667
[09:38] Timeout: connect to irc.aniverse.com
[09:38] Identd was Already On, Listening On Port 113, Replying as Minako***
[09:38] Trying server irc-1.aniverse.com:6667
[09:39] Timeout: connect to irc-1.aniverse.com
[09:39] Identd was Already On, Listening On Port 113, Replying as Minako***
[09:39] Trying server irc-4.aniverse.com:6667

As you can see, different things happening, it doesnt make sense. Any help with this issue? System is WinXP on 24/7 LAN connex

[ppslim]

Your post seems to go on about 2 questions, but only progresses onto 1 full question.

Disconnections can be caused by many things.

If you are not seeing a pattern in the disconnections,a nd the messages it returns, then it's likely only a routing/timeout problem.

Possibly increasing the timeout would help.

Second. You go on about launching bot.exe from another bot.

Have you done this yet, or is this still in planning?

I will tell you now, if you have done this, it is a possible cause of your problems.

The commands used to launch applications from within Tcl, can and will block either the application in question, or the launching programm, if not programmed correctly. Even more so on a windows machine.

Windrops do not go into the background on windows, so STDIN and STDOUT are allways in constant use.

This means that a channel opened with the open command will allways be open, till the bot dies. If the buffer is not read, then it's contents will fill up, until the second eggdrop can't place any more ifnormation into it.

With the exec command, the first eggdrop will block untilt he second bot crashes, or it terminated va .die. This is because this command waits untilt he prgram it calls finishes, until it returns.

I don't know what will happen to either bot in the open method.

On *nix, you may have simalar issues, though may not be as bad.

For windows, you could allways try using the schedual system, in replacment to cron jobs.

[Weirdo]

[09:38:38] <Minako> [09:38] Trying server irc-1.aniverse.com:6667
[09:39:39] <Minako> [09:39] Timeout: connect to irc-1.aniverse.com
[09:39:39] <Minako> [09:39] Identd was Already On, Listening On Port 113, Replying as Minako***
[09:39:39] <Minako> [09:39] Trying server irc-4.aniverse.com:6667
[09:40:30] <Minako> [09:40] Identd: Connect from 65.57.64.224:55178...
-
Error receiving data
-
DCC session closed

Well, thats what my DCC partyline picked up from this end. Cant be a problem recieving data, since its on the same machine. I havent implemented anything yet. I use a mirc script currently to run minako when i at home, just trying to make it remote so i can reboot minako or natsuki from university in case they crash again.

But is it worth it if the exec runs like that? hmmmmmm

[ppslim]

It might be worth trying a different version of windrop, to rule out any bugs.

[Weirdo]

From what i can tell, 1.6.12 did it, 1.6.13 did it. Although 1.6.10 i dont remember doing it. But there might have been an instance or two.

Its very strange indeed

It happens less to Natsuki, which is my other bot, she has no real scripts loaded, but she still suffers the same errors now and again

Believe it or not, i dont think 1.6.11 CVS had the bug. Natsuki used to stay online when minako crashed when she was running that.

Weird tho

[ppslim]

CVS versions are not real, and will vary from one second to another.

It's designed to centralise the storage, retrieval, back porting, branching and editing status of a code tree.

As such, you could download a version fo a file one second, and it has changed by another coders update another.

It would be the patch level we would need to know, as patch.h is updated to reflect any changes, and will tell you the last patch applied.

[Weirdo]

I checked on the old bot's log files, it was at the time i think

UPDATES1.6,v 1.373 2002/07/09 05:46:34 guppy

Got that from the updates file.

10th July was the version when i made the bot