RE: rhn_register / up2date hacking

Instead of modifying the clients, I made a script that I run on a new client that drops in my key, and updates /etc/sysconfig/rhn/up2date & rhn_register with the info for my current server.  I end up still doing the manual registration process though...  I then run my config script whenever the up2date / rhn_register rpms get updated and my script is independant of those RPMs..

	-----Original Message----- 
	From: Jeremy Johnson on behalf of Jeremy Johnson 
	Sent: Wed 5/29/2002 2:08 PM 
	To: [email protected] 
	Cc: 
	Subject: RE: [Current-server] rhn_register / up2date hacking
	
	
	you could use lvs for multiple servers, or if you had the money and resources use an alteon load balancer, with lvs you could just have one of the current servers be the load balancer to 1 other or a few other current servers, and load balance by wieght or round robin.....just an idea

		-----Original Message----- 
		From: Hunter Matthews [mailto:[email protected]] 
		Sent: Wed 5/29/2002 1:57 PM 
		To: Current Server Mailing List 
		Cc: 
		Subject: RE: [Current-server] rhn_register / up2date hacking
		
		

		I've generally not wanted to modify the clients.
		
		As a (large) side project, I'd change my mind if someone could figure
		out how to teach the client how to access multiple servers (a la
		apt-get)
		
		The only modifications I do here are config files and the attached
		rhnreg_ks.
		
		rhnreg_ks is a command line version of rhn_register, and this version
		has been modified with a --anon option that
		
		<wait for it>
		
		anonymously registers you against a current server. Since thats the only
		mode we support at this moment, it saves all that useless typing.
		
		This is a modified rhnreg_ks from 2.7.11, but I can't imagine why it
		wouldn't work with a 2.7.6x version of up2date.
		
		
		On Wed, 2002-05-29 at 14:49, Jeremy Johnson wrote:
		> what kinda modifications are you talking about? i made my own rpms, and kickstart installation to interact with rhn_register
		>
		>       -----Original Message-----
		>       From: Patrick Devine [mailto:[email protected]]
		>       Sent: Wed 5/29/2002 11:44 AM
		>       To: [email protected]
		>       Cc:
		>       Subject: [Current-server] rhn_register / up2date hacking
		>      
		>      
		>
		>
		>
		>       I was just wondering whether anyone on the list had done many (any?)
		>       modifications to rhn_register or up2date and whether there were any
		>       caveats to look out for.
		>      
		>       --Patrick.
		>      
		>      
		>       _______________________________________________
		>       Current-server mailing list
		>       [email protected]
		>       http://lists.dulug.duke.edu/mailman/listinfo/current-server
		>      
		>
		--
		Hunter Matthews                          Unix / Network Administrator
		Office: BioScience 145/244               Duke Univ. Biology Department
		Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
		Never take candy from strangers. Especially on the internet.