Hi there... the freeBSD server that my eggdrop was running from reebooted and the bot should restart but it didnt, now when I try to start the bot up again manually... ie in my case ./eggdrop botconf.txt... it tries to load up but ends with this error: Invalid userfile format.
Well it sounds like your userfile got messed up. Eggdrop makes a backup user file (blah.user~bak).If you delete your user file and rename your *.bak you should be able to restart your bot, if not you will need to delete the user files and restart your bot in userfile creation mode (-m) and readd your users.
<font size=-1>[ This Message was edited by: fudded on 2002-04-04 03:50 ]</font>
when a system reboots its supposed to send a kill msg to all processes and wait a few seconds before shutting down for this reason. Either the system is sending a harsh kill msg that kills it right away, or its simply not giving enough time before it actually shuts down after sending the msg (most likely cause the 100's of process are all franticly tryin to save at once). Either way its the shell providers fault. Think about tryin out a new one... Another factor, reliable shell providers shouldnt be rebooting often. Maybe email the admin and let him know.
_________________
Heavy rotated.
<font size=-1>[ This Message was edited by: nitroboost on 2002-05-02 23:26 ]</font>
Does this applies even to a bot that has been running for months with no problem with userfile before? Even the bot was killed or..., the userfile aren't not supposed to maintain as it is instead of clearing off all the users? Thanks.
Hmm... sorry i didnt really understand that 2nd part, but even if its up for a year yes, its still the shell provider at fault. Does your bot have a grip of users? The file could be perfectly fine, but when it recieves the kill msg it starts to save, and then the system shuts down before its done, leaving a corrupted userfile. If you shell was up for so long before it happened, then whats the problem with renaming a file once every 3 months.
The userfile gets corupted for the reasons that nirtoboost sugested.
As for a better fix than using the .bak files. What do you think they are for?
If a file is corupted, then it is corupted. There are no 2 ways about it. The eggdrop userfile is a text based format, which has no automatic fallback protection.
You must remember that eggdrop is a IRC Robot, and not a file replication system.