Re: Current 1.0: success on Solaris 8..

Hunter Matthews <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <1016469694.1145.9.camel@kea>
On Mon, 2002-03-18 at 07:18, Vincent Cojot wrote:
> 
> Hello everyone,
> 
> 	It took me more time that I would have liked but I am happy to
> report that I have a current server working fine from a Solaris 8 (sparc)
> server.. In my case, the server which used to collect all of the Redhat

Amazing. Congratulations!

> updates is a SUN server with their NFS implementation.. Therefore, the
> idea was to try to figure out if it would be possible to run a current
> server on that box.. The most difficult task was clearly to get all of
> current's software requirements to function properly on Solaris 8 (to name
> some of them: python (with bsddb), rpm, db-3.1, etc..).

The specific bsddb that we use is the 1.85 variant - 1.85 interfaces are
provided by all the many sleepycat variants, and that is the interface
that python uses by default.

> 
> Only problems that I encountered are:
> 
> 1) In current.init, the invocation of stunnel is wrong (I think):
>         daemon stunnel -d $CURRENT_HTTPS_PORT \
>                        -r $CURRENT_HTTP_PORT \
>                        -p $CURRENT_KEY_FILE \
>                        -P /var/run/stunnel.pid
> 
> Should be:
>         daemon stunnel -d $CURRENT_HTTPS_PORT \
>                        -r $CURRENT_HTTP_PORT \
>                        -p $CURRENT_KEY_FILE \
>                        -P /var/run/

Stunnel, at least the one commonly used on Linux, will take three
arguments for -P a) a specific filename, b) a directory to put a file 
generated by "service_name.port.pid", or c) none.

That might allow people to use multiple stunnels on the same box, so it
might be worth the change.


> 
> This gives me a pid file named: /var/run/stunnel.8080.pid
> 
> 2) Perhaps a Python-2.2 vs. current-1.0 problem but rebuilding a DB has a
> minor display glitch:
> 
> Mar %2m 13:12:48 Adding kernel-enterprise-2.2.19-6.2.12.sparc64.rpm
> Mar %2m 13:12:48 Removing kernel-enterprise-2.2.19-6.2.15.sparc.rpm
> Mar %2m 13:12:49 Adding kernel-smp-2.2.19-6.2.12.sparc64.rpm
>     ^
>     \---(see "Mar %2m" instead of "Mar 17"...)

Uh, I'll have to test that here. I think I've got a 2.2 python built...

> 
> Whole procedure In short:

A lot of this should go to the upstream maintainers. 

-- 
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.