- clo-devel - mailman3.common-lisp.net

[clo-devel] cvsroot syncing regularly takes too long
by Erik Huelsmann 08 May '11

08 May '11

Hi, On new-cl-net, the "sync cvsroot" script is regularly exceeding its runtime window (which is 20 minutes). One solution could be to change the nice parameter (-20). I'm hoping that others have better ideas, like changing the script from polling to event-based, which would eliminate the need to check all files individually. Does anybody have some cycles to look into the options? Bye, Erik.

2 2

[clo-devel] Security update required for exim4
by Hans Hübner 07 May '11

07 May '11

Drew, it seems that the Debian distribution that is installed on tiger does not supply a very current version of exim4, and today a security hole was reported in the version that we are running. Is it possible to add a package source with up to date security fixes so that we can update exim4? Thanks, Hans

1 0

Re: [clo-devel] link to OTRS docs for mail processing
by Hans Hübner 07 May '11

07 May '11

Hi Erik, I have installed the otrs gateway at otrs(a)tiger.common-lisp.net - As otrs runs under a specific user ID and I did not feel like inventing a suid wrapper, I have implemented the gateway by an explicit exim configuration directive (see /etc/exim4/configure if you are interested). I sent a few test mails to that address, but otrs did not reply to them, and I don't have an account in otrs yet. Can you add that for me, please? Thanks! Hans On Sat, May 7, 2011 at 2:33 PM, Erik Huelsmann <ehuels(a)gmail.com> wrote: > Hi Hans, > > This link discusses it: http://doc.otrs.org/3.0/en/html/x2048.html > > Basically, you need to pipe the mail into 'bin/PostMaster.pl' (which > is in /usr/share/otrs :-l ) > > The docs are for OTRS 3.0 while we still run 2.4, but there are few > changes in this area. > > Bye, > > Erik. >

1 0

[clo-devel] Testing exim4+mailman+sa+greylistd setup on tiger.common-lisp.net
by Hans Hübner 07 May '11

07 May '11

When you're reading this, things should be in working order. -Hans

1 0

[clo-devel] testing mailman+exim
by root 07 May '11

07 May '11

nothing else

1 0

[clo-devel] Migration status 2011-04-26
by Erik Huelsmann 27 Apr '11

27 Apr '11

Although last week's attempt to run cl-net off a network FS failed, this weekend a renewed attempt succeeded. This means we'll have completely current data on both old and new cl.net. This provides a solid basis to start migrating different services to the new machine. One of the things currently being moved is the ssh authenticated access. Other services to migrate soon are: * trac.common-lisp.net * paste.lisp.org / the bots * www.common-lisp.net / the webserver setup (with proxies and all) * the cron jobs * MTA/mailing lists * others Stelian and I are working through the steps and issues slowly on #tech.coop; if you want to discuss with us or want to know about progress or help out, come to the channel, hang around and join our efforts. Bye, Erik.

3 2

[clo-devel] clnet down?
by Marco Antoniotti 19 Apr '11

19 Apr '11

Hello is clnet down while you are doing the move? I cannot get to it. -- Marco Antoniotti

2 1

[clo-devel] File ownership: uid/gid design issue
by Erik Huelsmann 18 Apr '11

18 Apr '11

While browsing around, I noticed that we may have an issue with file ownership for Trac (but maybe wider): all files in a specific project under /project are owned by the project initiator with the group set to the unix group by the same name (all project files are world readable). This applies to all files, including Trac database. The problem arises when Trac (running as www-data under the http server) wants to modify the Trac database in the project. Since the user and group are set to values other than www-data, it can't write to the database file. In the specific case of Trac, this may probably be solved by running it against a postgresql backend instead of sqlite. However, possibly, other services [provided now or in the future] may require write access too. What's the usual way to solve this issue? Do people add the www-data user to all project groups? That doesn't seem right from the security perspective. Bye, Erik.

3 2

[clo-devel] 2011-04-15: cl-net migration progress
by Erik Huelsmann 17 Apr '11

17 Apr '11

My work on cl-net migration got stuck a little on tech.coop internal work this week. However, I'm fully back to the migration and I'm making copies of /project and /home right now. I suppose I'll be creating a copy of much inside /custom too, when the other two transfers have finished. At the same time, I'm trying to figure out how to best migrate /etc/password- and /etc/group-. Anybody here done someting alike before? I mean, I can't just copy it over, because the system accounts shouldn't be overwritten. I suppose a 'grep -v' (for inverse matching) should get us quite far filtering out system (uid<500) accounts. Another issue I'm thinking about is that we're going to switch to subdomains for hosting our services. However, the benefits of such a change seem low if we don't switch to a structure where our data is also grouped per service. Currently everything is in /project, which is grouped around projects, requiring all services to run on a single server because they need to access specific directories - one in each project. I'm thinking we should reverse the design: grouping data per service and making /project a set of symbolic links into the service directories. That way, all that's required is that the links point to the right locations in the file system, possibly NFS mount points, if the service were to run on a different server. Again, I'm interested in your comments and ideas. Regards, Erik.

4 5

[clo-devel] cl-net /custom/backup/old-projects directory?
by Erik Huelsmann 16 Apr '11

16 Apr '11

In the /custom/backup directory, there seem to be a number of old projects being archived. However, I doubt this is really useful: nobody can see that they ever existed in that location, so nobody can ask to be assigned maintainership of them. These are the projects I'm talking about: alpaca blitzblog clark clazy cl-darx cl-finance cl-me clotho cl-plus-j cl-torrent cl-trance gnucard hansa2 kmachine-cl monetdb-mapi ninep openAIR patg progintellect qrita xuriella Should we rather just delete these projects? Or reinstate them and create a page listing all inactive projects for which interested parties can ask to be assigned maintenance role/ commit access? Bye, Erik.

2 2