The package gpg-pubkey-b481ca4d listed in the installation-guide is not part of the SLES9. I think the package that is ment is the "suse-build-key".
But my problem now is that I have a nav3rc1 running on SLES, and everything "seems" to be running except web-interface and Alertengine.
I have used the SuSE rpm package. And is trying to find whats wrong with the apache-config. I have tried to look at the http://svn.nav.ntnu.no/nav/navme/trunk/doc/apache/httpd2.conf.example
But the apache-structer is totaly different from my debian-nav3-beta10 installation. Anyone have a suggestion where to start?
/usr/local/nav/bin/nav status networkDiscovery: Up cricket: Up eventEngine (pid 6435) is running... iptrace: Up backup: Up servicemon.py (pid 6467) is running... smsd.pl (pid 6491) is running... thresholdMon: Up mactrace: Up logengine: Up safe_smsd: Up Alertengine is not running.
maintengine: Up pping.py (pid 6520) is running... getDeviceData (pid 6546) is running...
Peder Sefland
Morten Vold morten.vold@ntnu.no 23.06.05 13:04 >>>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/06/2005 11:42, Peder Magne Sefland uttered:
But a search on google show me that SuSE Linux Professional 9.3 has this package. Has this document been writen based on Professional 9.3 or SLES9 ?
The document was originally written for SLES9, but I see Tristan Rhodes has edited the page since then - specifically he altered the part about manually installing Perl-DBD-Pg into installing it from Yast [1]
I haven't confirmed that his changes were valid, but if the perl-DBD-Pg package really isn't part of standard SLES9, then that part of his page change should be reverted.
Can I use the Professional 9.3 perl-DBD-Pg-rpm on my SLES9?
Don't know, you'll have to try it and see for yourself.
[1] http://metanav.ntnu.no/moin.cgi/InstallingOnSLES?action=diff&date2=11120...
- -- Morten Vold NTNU ITEA Integrasjonsgruppen