![](https://seccdn.libravatar.org/avatar/26ea09fce44f5a346284072691840633.jpg?s=120&d=mm&r=g)
Hi Victor, Sorry to you and to everybody else. It looks that I've mixed up something. My cited reference to the SuSE hotline was incorrect. The suggestion I've got to my question was just a direct private email by somebody who answerd to my posting in the german mailing list. The SuSE hotline did not answer till now. I've just checked all the update directories too. You are correct, there are no mod* rpms. My concrete problem with Apache 1.3.17 was, that the startup-script looked for a file rc.status, which is not on my system. I could start the demon directly, but there were indeed problems with the modules, that were not initiated correctly. Erich
I'm one of those others, who tried to update his SuSE 6.4 standard
to Apache 1.3.17 from the update directory without success. And I contacted
installation the
SuSE service-hotline. Florian Effenberger answerd and told me I need to update all the dependend packages (mod*, apache-contrib, ...) too.
Erich
I have been bitten by the same bug. I did not see any mod* rpms in the update directories though. Oh well, it is only a test server anyway.
Victor Cardona