On Fri, 27 Jul 2007 20:07:58 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Jul 2007 10:22:20 +1000 David Seikel <[EMAIL PROTECTED]> > babbled: > > > Another option would be for whoever has control of the mailing list > > to simply add [EMAIL PROTECTED] Set it up so that they > > can post, but don't receive email. > > we have this for cvs-commits. in fact you should possibly send to > cvs-commits? we can set up a new list - but i am not sure we need to > really? enlightenment-cvs is a good place to put it, as this relates to the CVS commits, and people interested in that subscribe to that list. > > The next hoop is that sf.net will then check to see if a user called > > onefang is allowed to send email from enlightenment.org. Once > > again, easydns.com may be able to help us jump through this hoop > > with their email forwarding service. > > > > In my testing I've never gotten past this hoop, so I don't know what > > other hoops there may be. Typically there is no response from these > > hoops, nothing ever gets bounced, and nothing is ever left in log > > files we can check. So the hoop jumping has to be done blind. > > > > Actually running our own SMTP server on e2.enlightenment.org would > > help to solve these problems, but I doubt we want to do that. > > cvs-commits list mail gets through - kainx may be able to help as he > manages the dev server that sends the mail that goes to cvs-commits. > see the commit.pl to see how it sends the mail too (in CVSROOT) commit.pl uses a method that was closer to my original efforts than what the nightly build has drifted to. I've changed the nightly build method back and it works as well as it used to. The resulting email still has to navigate the treacherous sf.net waters. Would not surprise me to find that KainX has a proper email setup on that server, instead of MX records that point to his DNS provider like e2 has. We should do the same for e2. I note that KainX has an e2 account and already has sudo. Care to help out KainX? For now I've got an evil hack setup. I still send the emails to myself, the difference is that instead of manually resending it, my email client does that automatically. Obviously only a temp solution, but at least it's fully automated. B-) > > Speaking of cron jobs, since it needs to run as root anyway if we > > are to use ionice, I propose sticking a suitable named script > > into /etc/cron.daily. It should run last, after all the useful > > system cron jobs have finished. Calling it zz_nightly_build should > > do the trick. > > > > What do the people that actually maintain the server think? > > you can run the build script - sleep for 10 seconds then sudo ionice > the PID How is that any better than what I originally proposed - sudo ionice -c3 su onefang -c NIGHTLY_BUILD sudo is still involved, you just complicated things with PID tracking and made a ten second window where the script can grind the machine to a halt. /etc/cron.daily/zz_nightly_build has the advantage of being easy to track down by later sys admins. It runs nightly, it needs root privs to start with even though it drops those very quickly, and it's the standard place for such things. > we probably should set up a user called ebuild that runs this stuff > actually - not run as root or as onefang :) Once we have the basics running, then we can sweat the details. B-)
signature.asc
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
