Here is a new rc-script for eggdrop Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** Bug 37670 has been marked as a duplicate of this bug. ***
Created attachment 23468 [details, diff] patch against 1.6.15-r1.ebuild to add eggdrop rc-script please rename previous rc-script as eggdrop.init, and place it in net-irc/eggdrop/files
Created attachment 23469 [details, diff] patch against eggdrop-installer to install rc-script for created bot this script mean to be run as root now, since the eggdrop user is created in the ebuild, and used as the default user (and then home) for this script
Created attachment 23470 [details] the rc-script to be placed in net-irc/eggdrop/files
i hope i'm not alone when i say i would mark this as WONTFIX seems like we'd be holding the users hand WAY too much in terms of setting up/running an eggdrop ...
yeap, so we can remove all the ebuilds... downloading, conf'ing and compiling all the packages at hand... so why Gentoo while LFS? ;) I don't understand your point of view. It's just a facility to start an eggdrop, not to configure it. Since there are lines like "die..." in the eggdrop.conf, you must look at it. At the end of this ebuild, eggdrop can't run anyway. I agree with you with the setting up of an eggy but not the starting... that's boring to: su - eggdrop && cd .eggdrop/bot && ./eggdrop... no? :)
it should preferrably be run from the users crontab anyhow, along with botchk. *shrug* anyhow this was a blasphemic thing (config inside the main scripts force you to modify them, which is bad) and pretty much a misues of the whole functionality.
Which script? The rc-script? No you don't modify it. You just copy one, and append the name of the bot like the net.* rc-scripts (which is done with my version of eggdrop-installer). With my updates you create eggies like this: run eggdrop-installer <botname> to install a new eggy directory in ~eggdrop/.eggdrop/<botname> and to create a eggdrop.<botname> corresponding rc-script, that's all. rc-scripts are made to start daemons, isn't it? And some cron daemons doesn't support the @boot tag so... do you start your ftpd with crond? :) I dont understand where is the misuse of the whole functionality
how many people run eggdrops under the 'eggdrop' account ? that's just asking for trouble on some networks, especially when you run more than 1 bot under user@host as for your cron daemon not supporting @boot, then switch ... in order for this script to be useful you have to be the owner of the box and exclusive user of the eggdrop ... which means you have full control over the box like spider said, the very common way of running bots out there is via crontab, and there are PLENTY of docs for how to do exactly that ... there are 0 docs for this, thus for the # of people who would actually switch to using this is not enough to make it useful
since I am the owner of the box housing my eggies, that's useful ;) ok, ok, you're right :)
I agree with spanky here, most eggies are run from a users cron script. So an init script is not partiucalarily useful right now. If you have multiple eggdrop bots as well then you would have to modify the init script as well. Thanks for your work though.
I agree with him too. However, for multiple bots you don't need to modify the script, just copy it with the appended botname (like the net.* scripts), that's all. :) Cheers Ludovic
