[cvsnt] How to net stop/start CVSNT on Redhat Linux ES4?

[r.pedroche.novillo at accenture.com]

  I do not think the first option will work at all.

  Stopping xinetd should be more than enough to ensure a stable
repository. I do not think there is any need to stop cvslockd.

  In fact, it is fairly overkill: it could be that other services are
hosted by xinetd (although in current Linux installations there are less
and less inetd-based services).

  A more elegant option would be to edit /etc/xinetd.d/cvspserver,
change the line "disabled = no" to "disabled = yes", send a SIGHUP to
xinetd, backup, undo modification and SIGHUP xinetd.

  Or, in RHES:

# chkconfig cvspserver off
(Backup)
# chkconfig cvspserver on

which will, in theory, do the same in less lines ;)

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of David Garcia
Sent: Friday, July 13, 2007 8:14 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] How to net stop/start CVSNT on Redhat Linux ES4?

Greetings,
   
  I see to do backups of a CVSNT repository on Windows you do a net
stop/start CVSNT,
  how to you do the same thing on Redhat Linux ES4? is it:
   
  service CVSNT stop
service CVSNT start
   
  -OR-
   
  wait for any cvs processes to complete that may be lingering
  stop cvslockd
  stop xinetd
  restart xinetd
  restart cvslockd
   
  Or something else altogether?
   
  Thanks in Advance, David
   

       
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.