egghelp/eggheads community

There is little that cane be done about this.

I would sugest switching networks, as this is obviously a bug in the IRCD than IRC itself.

What sort of action would you take on a user?

The quickest method I see is to create a botchk script used for crontab, and call that using your startproc system.

The problem is that you need to "cd" into the eggdrop dir, prior to running it.

Why not use a crontab?

Incidentaly, a message just cropped up saying they may delay this till early January (Hi wcc, wondering if you read this).

Nope.

It was/is hopped to be released by Xmas.

Only time will tell.

You need to setup your IRC client so you can debug the incoming CTCP request that initiates the DCC send. This sounds like a router issue, where the router can't perform loopback requests on your external IP. There is nothign you can do to fix this, without breaking DCC sends for other users. Besaid...

This means the userfile got currupted when being written or is blank.

These are signs that the file was open for writting then the shell rebooted.

Only a restore from the backup will fix this.

Eggdrop uses the first port defined as user connectable from the listen command.

This will be the firsy ALL or USER type listen,

The only real method is to pass a second argument with the length of the data.

This pretty much goes along the lines of putdccraw. You can pass and use embeded NULLs in the data. For it to function correctly, the length is passed.

simply comment out (add a # to the start of the line) the line that loads the module.

As noted, it gives very little benefit to you.

This means you have compiled your bot with the debug flag. When it dies, it creates this core file. The idea being that you can find out exacly what cuased it to crash by following which part of the code killed it. Your best bet is to delete this file, then recompile your eggdrop, though not from CV...

Wanna swop?

I was preying for a big bang and the lights fizzle out when they turned them all on.

Instead, we got a loud bang, sparks and a pop star - Sod the lights I tell ya

$arg contains the entire string passed to the proc.

Note, try feeding your script somthing like "!d test {test"

Note the error.

Your working with strings, but treating them like lists.

bobjuh wrote:It isn't even December yet

Try telling town planners that.

We have had our Xmas decorations in the town out for 2 - 3 weeks now.

You can only host one bot per port simple as.

You shoudl specify a a unique port for each and every bot. It does say that in the config file.