Change Request: database cleanup
by Toshio Kuratomi
A couple weeks ago we were having problems with xen13. db2 was on
xen13. We moved the databases that lived on db2 onto db3. That's been
working out pretty well as db3 was sized to run koji before the latest
round of koji optimizations so it's a pretty powerful box.
However, when we moved the databases we left out the scripts that clean
up the session tables for FAS. This means that everytime a user hits
one of our websites, it makes the FAS database grow. Currently the FAS
db is over 2GB in size with 860MB of that in the visit table.
We can't reclaim the space without running a vacuum full (or dropping
and recreating that table) which would mean downtime. However, we don't
seem to have any performance issues at this time so I'm mostly concerned
with the table continuing to grow rather than getting the space back.
I'd like to apply the following change in puppet which just installs the
cleanup script and cron job onto db3 where it can start working to keep
the visit table at its present level. When we switch back to having db2
separate from db3 we can disable this script on db3 and drop the fas2
database there (which will recover the space).
diff --git a/manifests/services/db.pp b/manifests/services/db.pp
index 8e7587f..e5a6409 100644
--- a/manifests/services/db.pp
+++ b/manifests/services/db.pp
@@ -52,6 +52,17 @@ class kojiDb inherits postgresServer {
source => "system/koji-cleanup-sessions.cron"
}
+ cron { db-cleanup-sessions:
+ command => "/usr/local/bin/db-cleanup-sessions",
+ user => postgres,
+ minute => 10,
+ ensure => present,
+ }
+
+ script { '/usr/local/bin/db-cleanup-sessions':
+ source => 'db/db-cleanup-sessions',
+ require => Package['postgresql8.3-server'],
+ }
}
class appDB inherits postgresServer {
-Toshio
15 years
wiki i18n
by Ian Weller
What is the status of wiki i18n? Last I knew Nigel was working on some
of that stuff, and that was four months ago, and I haven't heard a
single thing since.
--
Ian Weller <ianweller(a)gmail.com>
GnuPG fingerprint: E51E 0517 7A92 70A2 4226 B050 87ED 7C97 EFA8 4A36
15 years, 1 month
One click web based installation UI
by Abhradip Mukherjee
I presented this idea on GSOC 2009 project from Fedora on similar topic.
Then Toshio Kuratomi replied "Whether or not this accepted for GSOC, there
are some good ideas here. I think communicating with the PackageKit
developers [1]_ about how your ideas can tie into their ideas for
installing from the web is a good place to start if you want to support
arbitrary installing packages from arbitrary locations. Talking to me and
other fedora Infrastructure people on the fedora-infrastructure list[2]_ or
#fedora-admin on irc.freenode.net would be a good starting point if you only
want to let people install packages from official Fedora Repositories." So
here it goes with the parts of the conversation between me and Mr. Toshio
Kuratomi.
======================================
*== Why should we choose you over other applicants? ==*
In choosing me over other applications, you may like the following facts :
· I am very much passionate about FOSS which you can see from the
name I have given to the network I formed (Passion4Freedom)
· I have worked in real life FOSS campaigns in educational institutes
and formed a FOSS network in those institutes.
· I have the knowledge in working with Open Source CMS. This is an
added advantage in web projects like this one.
· I have knowledge in installing applications on Fedora using .rpm
files and by source compilation as well.
· I know shell scripting and other Linux programming languages.
· I have strong knowledge in C and C++ and basic knowledge about STL
and SystemC.
· I know Java, Servlet, JSP, EJB.
· I have knowledge on Javascript, HTML, CSS.
· I have done extensive work on LAMP architechture.
· I have used online installation services like Klick or Freespire’s
CNR . I also used easy install scripts for various programs
· I have been using Fedora for past 3 years and I have closely
understood the working of yum.
· I have done various personal researches on Fedora in VirtualBox
just to understand it better.
· I am desperate to contribute something useful to my most beloved
distro. I love you Fedora. F8 was my first love and I still love it more
than any other distro.
· I have already created a website for making installation easy on
fedora http://install.passion4freedom.07x.net (it is on a free server, so it
may be down sometimes, please consider). I hope that this will tell about my
idea in a more clear way.
*== Proposal Description ==*
Here is my proposal in detail:
** An overview of my proposal*
To create an online software archive for Fedora which gives the user a one
click install facility, my approach is based on community contribution.
Instead of going for a synchronized UI for repository, I created a drupal
based website that has an archive of software installer scripts for various
versions of Fedora. The archive is maintained by the community and they
update/comment on the software. The website is indexed and keyword searching
can be used to search the software of choice. The shell scripts are
executable text files with .qi extension. They are made in such a way so
that user can install it by executing just once. The whole archive can be
edited by ever member and any member can upload a new shell script for
installation of any software.
The proposal has been converted to a website already (
http://install.passion4freedom.07x.net ).
The cause for which I did not take up creating UI for repository is also
because I do not have enough technical knowledge about that. If GSOC mentor
provides me that technical guidance I hope it wont be much tough for me as I
have the right passion for freedom.
* * The need I believe it fulfils*
It makes software installation a lot easier to newbies and saves time for
pros. This is a requirement of all Fedora users and this should be
implemented as soon as possible as that will make the usability of Fedora
much more.
** Any relevant experience I have*
· Experience with Linux, Apache, MySQL, PHP.
· Experience with creation of social networking websites.
· Experience of creating simple installer shell scripts for fedora
apps.
· Experience with web CMS softwares.
· http://install.passion4freedom.07x.net can be viewed as an effort
along the same path.
** How I intend to implement my proposal*
· Wiki Style
· Drupal based
· Community maintained
· Downloadable shell scripts with chmod 777
· 1 click install for end users
** A rough timeline for my progress*
· Depends. If it is to be done in the way I am proposing then Fine
tuning to suit your needs is the only thing left. And that should not take
much time.
· If I have to build it as a synchronized UI to the repository then
as I do not have enough technical knowledge on synchronizing with repo, I am
not being able to estimate the timeline very well
· But, as a whole I can assure you that with the fire for freedom and
fedora within me, it will be easily converted into reality within the
timeline of GSOC (if not earlier).
** Any other details you feel we should consider*
· Online distribution customization following the paths of nimbleX
and Slax.
· Desktop tool for installing most important apps following the way
of automatix in ubuntu.
==================================================================================
On 6th April 2009 15:26 Toshio Kuratomi wrote:
I like the idea of having a simple way to install packages. However,
there's a few problems with the proposal.
1. The Package Database is a python application. We'd want to tie any
official installation of packages for Fedora into that so we need python
knowledge.
2. You need to talk to the PackageKit developers and Fedora
Infrastructure in order to find out what the constraints each group would
have.
3. From the Fedora Infrastructure side:
- We probably can't host arbitrary install scripts as we aren't able to
legally point to arbitrary packages. For instance, many multimedia codecs
are patented without licenses to be used in free software.
- We would want to avoid Drupal if we can. We already have the
PackageDB and this is most likely something we'd want to integrate there.
We've recently settled on Zikula for a CMS solution so if we needed to
implement something on top of a CMS platform, I'd rather we used that.
=====================
I replied:
> Personally, I think easy package installation with simple scripts is a
> better idea. For example to run .exe files it is more user friendly if I
> give a script to install wine, wine-doors, playonlinux all together instead
> of giving them a package UI where upon searching they will be able to find
> three different packages for the cause. Some people install wine and
> complain that wine is not able to play games but they dont install
> playonlinux as they just dont know abut it.
(This is just a part of my reply)
=====================
On 16th April 2009 21:41 Toshio Kuratomi wrote:
Yeah, I'm afraid it's a bit too late for GSoC 2009. But I'm glad to hear
you're going to work on your ideas some more. I can see what you mean about
trying to associate things that serve the same task (like wine, wine-doors,
and playonlinux). I'm hoping that tagging of packages and searching by tag
will help us get closer to that within Fedora with the official Fedora
repositories.
Letting people install things that aren't in the official repositories is
probably something that won't happen within Fedora but it could be useful
for a third party site to do. Building up and managing trust would be the
hard task in this regard, though, as it's easy to provide a script for users
to download and install arbitrary software on their computers but hard to
protect them in case either the scripts are malicious or the software the
scripts point at become malicious.
===================================
Here goes my final proposal :
"I have started the project at install.passion4freedom.07x.net with 100
students here at Kolkata, India. We hope to build it up soon. But I still
can not understand,why you guys are not able to back the project. As far as
I understand, if your main problem is that you can not depend on the user
community i.e. you are afraid that the users may upload malicious code, then
why not build a similar website which will not give the option to upload the
scripts to the users. Why dont we (you and I) take the responsibility of
creating such scripts and let the users download the scripts. Let me explain
to you how great this thing can be. Suppose a user needs to download the
source code of the latest kernel. We can create a script to simplify his job
in the following way
1. Script asks the user where to store the file
2. cd "Specified DIR"
3. wget "kernel source url"
4. untar
5. open DIR in nautilus
This way user gets to use it with comfort. Otherwise if they had to write
each command by hand or had to find where the source code is (manually) and
how to untar it, they could have felt that using GNU/Linux is basically a
terminal job. I feel it will be better if Fedora offficially supports the
project as this project has the ability to simplify the whole procedure of
installation in GNU/Linux.
If you feel I am wrong, please comment on where I am getting it wrong?
Also, I know that there may be legal issues for supporting installation of
Flash and other properietory thing. But why not simplify the normal
installations, even if we can't proceed with the properietory ones.
I still have a confusion. Why will there be legal issues if we proceed in
the following way :
A person wants to install Flash
We provide him a script which will
guide him to the website of flash with a text mode browser
Upon accepting the license script asks him "where to save the file"
after downloading the file, script installs it immediately
Spot the difference with the options available now. In this way the person
feels the same way that he used to feel when he used to install softwares on
his previous popular properietory distribution. Here also he needs to accept
and press enter to move to the next step (The next-next feeling is what I am
talking about). Also he gets the feeling that here the case is even better
as the installer not only downloads the file but also installs it at a go.
He will feel that it is easier to use GNU/Linux.
This project will make s/w instalation on GNU/Linux systems much more
easier. If fedora provides support and expertise, I feel it will soon become
a useful contribution to Fedora community and will certainly become a
reliable service. I hope you guys get my point. Please comment."
Please reply.
15 years, 1 month
Out for the next couple of days
by Mike McGrath
I'm moving tomorrow which means I'll be largely unavailable over the next
several days. I'll be able to make my way to a starbucks for internet
and stuff for emergencies but other then that probably won't be around
much.
-Mike
15 years, 1 month
Meeting Log - 2009-04-16
by Ricky Zhou
20:00 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Who's here?
20:00 * ricky
20:00 < ggruener> ping
20:01 -!- pingou_ [n=Pingou@fedora/pingou] has quit Client Quit
20:01 < ivazquez|laptop> Pong.
20:01 < johe> pong
20:01 < sts> pong
20:01 * SmootherFrOgZ is
20:01 * nirik is in the cheap seats in the back.
20:01 < mmcgrath> k, lets go
20:01 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Tickets
20:02 < mmcgrath> .tiny https://fedorahosted.org/fedora-infrastructure/query?status=new&status=as...
20:02 < zodbot> mmcgrath: http://tinyurl.com/47e37y
20:02 -!- yingbull [n=yingbull(a)S01060013104275dd.ss.shawcable.net] has joined #fedora-meeting
20:02 < mmcgrath> k, seems there's no tickets to discuss
20:02 < mdomsch> whee
20:02 < sts> easy ;)
20:02 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Preview Relase
20:02 < mmcgrath> So we're frozen again for the preview release.
20:03 < skvidal> yay for frozen
20:03 < mdomsch> that was quick
20:03 < mmcgrath> mdomsch: yeah the closer we get the less time we have to do stuff :)
20:03 < mmcgrath> both good and bad I suppose.
20:03 < ggruener> how long?
20:03 < mmcgrath> ggruener: they always start two weeks before the release and end one day after the release.
20:03 < mmcgrath> So they are typically 2 weeks + 1 day.
20:03 < mmcgrath> but if a release slips, then the freeze-end slips with it.
20:03 < mmcgrath> which does happen from time to time.
20:04 < ggruener> k
20:04 < mmcgrath> f13: you around?
20:04 * mmcgrath wonders exactly what "Compose & Stage Release Candidate" means.
20:04 < mmcgrath> jwb: you know?
20:05 < jwb> essentially, create the ISOs and get them pre-staged on the mirrors
20:05 < mmcgrath> well, I'll ignore that for now.
20:05 < mmcgrath> ah
20:05 < mmcgrath> jwb: k
20:05 < jwb> why do you ask?
20:05 < mmcgrath> and we're doing a full release for the preview release right?
20:05 < mmcgrath> jwb: just checking.
20:05 < jwb> i think so...
20:05 < mmcgrath> the preview goes on the mirrors and stuff, not just torrent?
20:05 < jwb> i think so, but f13 would know for sure. or notting
20:05 < mdomsch> yes
20:05 < mmcgrath> k, thought so.
20:06 < jwb> don't listen to mdomsch. he doesn't know. he's not 1337
20:06 < mmcgrath> I'm going to get the tickets created
20:06 < jwb> ;)
20:06 < mmcgrath> http://fedoraproject.org/wiki/ISOP:RELEASE
20:06 < mdomsch> 120GB free
20:06 < mdomsch> which should take it
20:06 < mmcgrath> that should do for the preview, what about the final release?
20:06 -!- RodrigoPadula [n=Rodrigo(a)200.242.89.130] has quit Read error: 60 (Operation timed out)
20:06 < mdomsch> but we'll want to nuke F11-Alpha at some point
20:06 < mmcgrath> mdomsch: FYI, our new mirror system should be ready to be installed in early May.
20:07 < mmcgrath> but our release schedule might block some of that.
20:07 < notting> honestly, given beta's gone out, i'd say we can nuke alpha whenever
20:07 < mdomsch> notting, +1
20:07 -!- tibbs [n=tibbs@fedora/tibbs] has quit "Konversation terminated!"
20:07 < sts> mmcgrath: what parts of the infrastructure are frozen?
20:08 < mmcgrath> k, so that's good to know.
20:08 < mmcgrath> sts: to find out just check out - http://fedoraproject.org/wiki/ISOP:RELEASE#Change_Freeze]
20:08 < mmcgrath> err http://fedoraproject.org/wiki/ISOP:RELEASE#Change_Freeze
20:08 < sts> thx
20:08 < mmcgrath> sts: this is a pre-release freeze, not the full freeze.
20:09 < mmcgrath> mdomsch: FYI, the mirror upgrade will be online in PHX1 but require downtime in RDU.
20:09 < mdomsch> mmcgrath, how long?
20:09 < mmcgrath> mdomsch: so when they're ready I'll work with you and releng to decide if it's worth it to us to wait until F11 is out the door or not.
20:09 -!- rdieter_laptop [n=rdieter(a)pcp088952pcs.unl.edu] has quit Remote closed the connection
20:09 < mmcgrath> mdomsch: no idea yet, I was talking about it in a meeting yesterday but didn't discuss with the actual tech that will be installing it
20:10 < mdomsch> I'd expect it to be brief
20:10 < mmcgrath> I would too, certainly measured in 'hours' and not 'days'
20:10 < mdomsch> unmount old nfs share, mount new nfs share
20:10 < mdomsch> we'll just need to warn mirror-list-d
20:10 < mmcgrath> well, there's going to be a sync in the middle there :)
20:10 < mdomsch> sync first
20:10 < mmcgrath> yeah, I'm going to make sure that happens properly
20:10 < mmcgrath> mdomsch: one thing I don't know is if they have room for the old netapp and the new netapp or if they have to remove the old for the new.
20:10 < mdomsch> and only folks hitting download-i2 would be affected anyhow
20:11 < mmcgrath> Some of these details I'll have to work out with them.
20:11 < mmcgrath> yeah
20:11 < mmcgrath> mdomsch: the bad part of the mirror upgrade is it means what was the TPA filer won't come online until the rest of this is all figured out.
20:11 < mmcgrath> they're doing some strange setup in PHX2 that we're apart of.
20:11 < mmcgrath> it should be transparent to us but it's taking them longer to get that stuff online there
20:12 < mdomsch> mmcgrath, I'd love to get rsync logs from download*
20:12 < mdomsch> see who is actually hitting us directly as opposed to the tiers
20:12 < mdomsch> and on what kind of schedule
20:12 < mmcgrath> mdomsch: ticket submitted, I'll let you know what they get back to me with
20:13 < mdomsch> cool thanks
20:13 < mmcgrath> k
20:13 < mmcgrath> well while we're all here, lets get the tickets created.
20:13 < mmcgrath> ricky: you around?
20:13 < ricky> Yup
20:13 < mmcgrath> ricky: you going to do the web page as usual?
20:14 * mmcgrath gets to generating - https://fedorahosted.org/fedora-infrastructure/report/9
20:14 < ricky> I'll get it setup beforehand, but I might not be around to release it as usual
20:15 < mmcgrath> ricky: k, no worries, once the page is created just put the directions in the ticket and someone will nab it.
20:15 < mmcgrath> I'll do the mirror space verification though I think we're fine (we were just talking about it.
20:15 < mmcgrath> For those that don't know, we're talking about the tickets listed here -
20:15 < mmcgrath> http://fedoraproject.org/wiki/ISOP:RELEASE#Preparations
20:16 < mmcgrath> I'll take the release day ticket, it's a tracker ticket
20:17 < mmcgrath> SmootherFrOgZ: you want to do the mirror permission verification again?
20:18 < SmootherFrOgZ> mmcgrath: yeah, assign it to me
20:18 < mmcgrath> SmootherFrOgZ: will do
20:18 < mmcgrath> mdomsch: do you want
20:18 < mmcgrath> .ticket 1338
20:18 < zodbot> mmcgrath: #1338 (repo redirects) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1338
20:19 < mdomsch> mmcgrath, sure, it's done already
20:19 < mmcgrath> mdomsch: when does that get done? is it automatic or are you just that on the ball with it? :)
20:19 < mdomsch> I did it for all the releases when I had to do it for one
20:19 < mdomsch> I suppose I could make that automatic...
20:20 < mmcgrath> no worries, just curious.
20:20 < mmcgrath> mdomsch: and how about
20:20 < mmcgrath> .ticket 1340
20:20 < zodbot> mmcgrath: #1340 (Add new release to mirror manager) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/1340
20:20 < mdomsch> mmcgrath, I just updated the SOP for 1340 - that's automatic now
20:20 < mmcgrath> sweet
20:20 < mdomsch> only if it somehow doesn't fire do we need to take any action
20:21 < mmcgrath> ricky: go ahead and accept 1334
20:21 < mdomsch> e.g. the versioning scheme changes yet again
20:21 -!- RodrigoPadula [n=Rodrigo(a)200.242.89.130] has joined #fedora-meeting
20:22 < mmcgrath> mdomsch: <nod>
20:22 < mmcgrath> Ok, I'd expect the preview release to go just as smooth as the beta release.
20:22 < mmcgrath> Anyone have any questions or concerns wrt the preview release?
20:22 < mmcgrath> http://fedoraproject.org/wiki/Schedule
20:22 < mmcgrath> that's the global schedul
20:23 < mmcgrath> while the beta slipped I don't think the preview is set to slip right now
20:23 -!- EvilBob [n=EvilBob@fedora/bobjensen] has quit Remote closed the connection
20:23 < poelcat> no everything else is holding to original schedule
20:23 < mmcgrath> poelcat: thanks
20:24 < mmcgrath> Ok, so that's it on the release for now, we'll discuss this again next week I'm sure.
20:24 < mmcgrath> So next topic...;
20:24 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Cloud
20:24 < mmcgrath> So the cloud stuff is coming along slowly
20:24 < mmcgrath> G, SmootherFrOgZ, the ovirt team and myself have been working to get our cloud up and going.
20:24 < mmcgrath> Lots of bumps but we've been getting through them.
20:25 < mmcgrath> Nothing too much to report here, i did my first guest install just an hour ago or so but now ovirt can't figure out the state of that guest :)
20:25 -!- sharkcz [n=dan(a)plz1-v-4-17.static.adsl.vol.cz] has quit "Ukončuji"
20:25 < mmcgrath> oh and there's a segfault in libvirt-qpid
20:25 < mmcgrath> other then that though we're making progress.
20:25 < mmcgrath> Any questions on the cloud stuff?
20:25 * johe has none
20:25 < mmcgrath> Ok, with that we'll...
20:26 -!- BaRRa [n=tmakinen(a)tk-cn0002.oulu.fi] has left #fedora-meeting []
20:26 -!- mmcgrath changed the topic of #fedora-meeting to: Infratructure -- Open Floor
20:26 < mmcgrath> anyone have anything to discuss?
20:26 -!- cassmodiah [n=cass@fedora/cassmodiah] has quit Remote closed the connection
20:26 < mmcgrath> Any of you new people want to say hello and introduce yourself?
20:26 * johe want to
20:26 < mmcgrath> johe: take it
20:27 < johe> So then, hello, i already intoduced myself on the mailinglist, so i think there is not much more to say,
20:27 * ricky waves
20:27 < johe> hoping we having a good working together
20:28 * johe /finish
20:28 < mmcgrath> johe: heh, that was quick but hello!
20:28 < mmcgrath> johe: how much time per week do you think you'd like to contribute?
20:29 < johe> mmcgrath, well cant say, i'am online many hours a day, if theres a way i can help i wlways will do, 10 to 20 hours should work, if you wanted to know a time :-)
20:30 < mmcgrath> johe: that's quite a bit, well things are in a bit of a lull right now.
20:30 < mmcgrath> But I'm sure they'll pick up after the freeze, stick around and get to know who does what.
20:30 < mmcgrath> sts: do you want to say hey?
20:30 < johe> will do so
20:30 < sts> yeah sure!
20:30 < sts> here i am ;)
20:31 < sts> i'm a systems engineer working at silverserver, an austrian isp
20:31 < sts> and i'm trying to get sponsored for fedora-noc.
20:31 < sts> already got my welcome mail...
20:31 < mmcgrath> sts: sweet, G_work and dgilmore are both from down under.
20:31 -!- RodrigoPadula [n=Rodrigo(a)200.242.89.130] has quit Read error: 54 (Connection reset by peer)
20:31 < sts> yeah, G already talked to me.
20:31 < sts> ;)
20:32 < mmcgrath> hehe
20:32 < mmcgrath> sts: ggruener is also just getting started in some sysadmin-noc work.
20:32 < mmcgrath> you two should talk after the meeting.
20:32 < ggruener> yeah that can we do:)
20:32 < sts> well, I gotta go right after the meeting, but i'd be pleased to talk to you tomorrow.
20:32 < sts> ;)
20:33 < sts> sorry mate..
20:33 < ggruener> np
20:33 < mmcgrath> sts: cool
20:33 < mmcgrath> Ok, well it looks like we'll be getting done a bit early this week but that's good.
20:33 < mmcgrath> If no one has anything else we'll close the meeting in 30
20:35 -!- mmcgrath changed the topic of #fedora-meeting to: Infrastructure -- Meeting end
15 years, 1 month
Fedora Calendering system: listing clear requirements.
by susmit shannigrahi
Hi,
The other mail was getting too long.
I am writing this as I think I have found the solution. (by using
zicula and phpical together)
So I want to understand the required functionalities.
What I have got so far:
1. Having a calender. ;)
2. Updating and Syncing from different clients using caldev protocol.
3. Having a web-interface to view/update/sync the calenders.
Right?
Thanks.
--
Regards,
Susmit.
=============================================
ssh
0x86DD170A
http://www.fedoraproject.org/wiki/user:susmit
=============================================
Sent from: Calcutta WB India.
15 years, 1 month
[Change Request] Add dirsec to rsyncd.conf on cvs1 for ticket 1327
by Kevin Fenzi
This seems like a pretty safe change, but it's my first puppet change,
so I might have messed something up. ;)
I also changed the comment on the pkgs rsync target as it was wrongly
saying it was the lookaside cache as well. I could revert that part if
it's thought to risky. ;)
---
modules/rsync/files/rsyncd.conf.cvs1 | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/modules/rsync/files/rsyncd.conf.cvs1
b/modules/rsync/files/rsyncd.conf.cvs1 index 356ffc8..93881dc 100644
--- a/modules/rsync/files/rsyncd.conf.cvs1
+++ b/modules/rsync/files/rsyncd.conf.cvs1
@@ -13,7 +13,14 @@ read only = yes
[pkgs]
path = /cvs/pkgs/
-comment = CVS Lookaside cache
+comment = Fedora packages CVS
+uid = nobody
+gid = nobody
+read only = yes
+
+[dirsec]
+path = /cvs/dirsec/
+comment = Dirsec CVS
uid = nobody
gid = nobody
read only = yes
--
1.5.5.6
15 years, 1 month
