From: Jeffrey A Law <law@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: overseers <overseers@sourceware.cygnus.com>
Subject: Re: cvsupd install
Date: Mon, 01 May 2000 11:44:00 -0000 [thread overview]
Message-ID: <15817.957206703@upchuck> (raw)
Message-ID: <20000501114400.YMklmGFTH-5lANpoet9IIbcRnlyL2-74XsJiwAhENtQ@z> (raw)
In-Reply-To: <390CDB74.5197199F@cygnus.com>
In message < 390CDB74.5197199F@cygnus.com >you write:
> (Perhaphs I should set up a cron job to send this e-mail out after every
> reboot :-)
> Could someone please do the following:
>
>
> Install the cvsup config:
>
> $ ( cd ~cagney && tar cf - cvsup ) | ( cd /sourceware && tar xf - )
>
> (yes this puts it on ``/'' if there is a better directory, please
> suggest :-)
Done. It's as good as any.
> Install/edit/test (as root...):
>
> ~cagney/bin/cvsupd.rc
>
> (in /usr/local/etc/rc.d/cvsupd.rc ?). The suggestion in the file is to
> send all log output to @local3 which is currently just rsyncd. Probably
> want to edit /etc/syslog.conf to hint that this is happening.
> Alternativly a separate loging channel could be allocated.
I've started it out of rc.local just for simplicity's sake. I'm not all
that familiar with the startup/shutdown facilities found in modern systems :-)
I haven't tested it though...
> Tweek /sourceware/cvsup/cvsupd.access to contain just:
>
> +0.0.0.0/0
>
> which, I think, gives everyone access.
Actually, I don't think we want to do this. The idea was to allow CVSup
for folks providing anoncvs mirrors, not for everyone.
> Tweek the ``how to create a project'' notes to mention that:
Done.
jeff
next prev parent reply other threads:[~2000-05-01 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Andrew Cagney
2000-04-30 18:20 ` Andrew Cagney
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-05-01 11:44 ` Jeffrey A Law
2000-12-30 6:08 ` Andrew Cagney
2000-05-01 16:12 ` Andrew Cagney
2000-12-30 6:08 ` Jeffrey A Law
2000-05-01 21:21 ` Jeffrey A Law
2000-12-30 6:08 ` Andrew Cagney
2000-05-01 21:49 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15817.957206703@upchuck \
--to=law@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=overseers@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).