From: Mark M. <mie...@gm...> - 2009-08-16 04:25:07
|
All, The Fedora Core 10, 64-bit rpm, worked fine on SuSE 11. Since David built a Fedora Core 11 rpm, I went to test that on Fedora 10 and SuSE to minimize the number of different rpms we needed. The Fedora 11 rpm worked fine on Fedora 10. But, when I tested it on SuSE 11, the install hung right after installing rxapid. Everything got installed and rxapi was started. It turns out that /etc/init.d/rxapid start hangs, on SuSE. I built a Fedora 10 64-bit rpm, and it also hung on SuSE. This used to work, so I think it has something to do with switching to nobody. I had already hacked rxapid several times to get it to work on Debian and SuSE. The change needed to get it to work on SuSE, now, looked to me like it would break on Debian. So, I just built the SuSE 11 64-bit rpm with a rxapid that worked. SuSE has its own LSB compliant init script conventions, with SuSE specific quirks. Very similar to Debian. I think for the next release and going forward we should try writing a LSB compliant rxapid script and see if it works on all the distributions we support. If it doesn't, then we probably need to write several different rxapid scripts, specific for each distribution. By the way, I don't have a 32-bit SuSE 11 installation, so I couldn't test that version. My suspicion is that none of the current 4.0.0 release rpms will work on 32-bit SuSE 11. If a user reports it as a problem, I'll put 32-bit SuSE 11 on a partition and build a rpm. Just didn't want to do an install if it is not needed. -- Mark Miesfeld |