I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- Does anyone know what this error is Sean
On Sunday 16 November 2003 20:52 pm, Sean Rima wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
Does anyone know what this error is
What's the application and what are you doing with it at the time?
Sean
-- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
Hi Dylan! On Sun, 16 Nov 2003, Dylan wrote:
On Sunday 16 November 2003 20:52 pm, Sean Rima wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
Does anyone know what this error is
What's the application and what are you doing with it at the time?
Sean
(Forgot about Mutt) It is a program called Irex which is for BBS/Fidonet use. I have a nasty feeling that because it is a stsic shareware linked program compiled on an old glibc that could be the problem, it is shareware and the source is not available. Sean
Hi people! I have to install proftpd on my SuSE 8.2 box. I got the package, and tried to install it : Suzie:/tmp # rpm -Uvh proftpd-1.2.9-1.9.i386.rpm error: failed dependencies: chkconfig is needed by proftpd-1.2.9-1.9 krb5-libs is needed by proftpd-1.2.9-1.9 libcrypto.so.4 is needed by proftpd-1.2.9-1.9 libssl.so.4 is needed by proftpd-1.2.9-1.9 perl(getopts.pl) is needed by proftpd-1.2.9-1.9 perl(strict) is needed by proftpd-1.2.9-1.9 I searched and 'wget'ed every missing dependency, then tried to install some of them : Suzie:/tmp # rpm -Uvh libkrb51-1.3-3mdk.i586.rpm file /etc/krb5.conf from install of libkrb51-1.3-3mdk conflicts with file from package heimdal-lib-0.4e-302 Every dependency returns a similar conflicting message. To tell frankly, I am used to BSD ports. What is the best practice to install an RPM package and assure dependencies existence? Will I have to go on the net and find every missing dependency everytime I need to install a RPM? Sometimes, I have to find dependencies for dependencies of the RPM I want to install, which leads to confusion and long search periods. They have to be an easier way to go? How could I resolve the 'conflicting' package issue? Thank you very much in advance, Regards, Steve
And this haw WHAT to do with Sean's error? When you send a new question to the list, please do not reply to an existing mail - it fscks up threaded email clients. -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
Hi Dylan! On Sun, 16 Nov 2003, Dylan wrote:
And this haw WHAT to do with Sean's error?
When you send a new question to the list, please do not reply to an existing mail - it fscks up threaded email clients.
I have to admit that it totally threw me when I seen it :) Sean
Op zondag 16 november 2003 22:38, schreef Hemond Steve:
Suzie:/tmp # rpm -Uvh libkrb51-1.3-3mdk.i586.rpm file /etc/krb5.conf from install of libkrb51-1.3-3mdk conflicts with file from package heimdal-lib-0.4e-302
Every dependency returns a similar conflicting message.
To tell frankly, I am used to BSD ports. What is the best practice to install an RPM package and assure dependencies existence? Will I have to go on the net and find every missing dependency everytime I need to install a RPM? Sometimes, I have to find dependencies for dependencies of the RPM I want to install, which leads to confusion and long search periods. They have to be an easier way to go?
How could I resolve the 'conflicting' package issue?
isn't heimdall another ftp deamon? In this case you can remove (rpm -e heimdall) and have the other (proftpd) installed. -- Richard Bos Without a home the journey is endless
On 11/17/2003 05:38 AM, Hemond Steve wrote:
I have to install proftpd on my SuSE 8.2 box.
It has to be that particular package? Having 8.2, I see it is not included (for a reason). I would recommend using vsftpd instead, but if you need that exact version, Try getting the src.rpm from 8.1 and rebuilding.
I got the package, and tried to install it :
From where. It is definitely not a package built for 8.2.
Suzie:/tmp # rpm -Uvh proftpd-1.2.9-1.9.i386.rpm error: failed dependencies: chkconfig is needed by proftpd-1.2.9-1.9 krb5-libs is needed by proftpd-1.2.9-1.9 libcrypto.so.4 is needed by proftpd-1.2.9-1.9 libssl.so.4 is needed by proftpd-1.2.9-1.9 perl(getopts.pl) is needed by proftpd-1.2.9-1.9 perl(strict) is needed by proftpd-1.2.9-1.9
I searched and 'wget'ed every missing dependency, then tried to install some of them :
This is because that package was built for a different distribution.
Suzie:/tmp # rpm -Uvh libkrb51-1.3-3mdk.i586.rpm file /etc/krb5.conf from install of libkrb51-1.3-3mdk conflicts with file from package heimdal-lib-0.4e-302
Heimdal is the SuSE keberos package. the above package is made for Mandrake.
Every dependency returns a similar conflicting message.
To tell frankly, I am used to BSD ports. What is the best practice to install an RPM package and assure dependencies existence?
Use Yast or apt-get, and stick to packages built for your system/distibution. Expect problems using other packages prebuilt binaries, which may be looking for files in different locations, different versions, etc.
Will I have to go on the net and find every missing dependency everytime I need to install a RPM?
SuSE comes with so many packages on the CDs/DVD, there shouldn't be that many needed elsewhere, and building the one you need are on option.
Sometimes, I have to find dependencies for dependencies of the RPM I want to install, which leads to confusion and long search periods. They have to be an easier way to go?
If you often need packages not included in SuSE, try apt-get. It will give you good dependency checking, and a bit wider source for packages. Sometimes, though, there are reasons a certain package, like proftpd, are not included. It is called security, and quality, which is why many of us buy SuSE.
How could I resolve the 'conflicting' package issue?
Either install vsftpd via Yast, if what you need is an ftp daemon, or if you need that particular package, get it from the 8.1 tree, or get the src.rpm and rebuild it. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hi Dylan!
On Sun, 16 Nov 2003, Dylan wrote:
On Sunday 16 November 2003 20:52 pm, Sean Rima wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
Does anyone know what this error is
What's the application and what are you doing with it at the time?
Sean
(Forgot about Mutt)
It is a program called Irex which is for BBS/Fidonet use. I have a nasty feeling that because it is a stsic shareware linked program compiled on an old glibc that could be the problem, it is shareware and the source is not available. I would concur. SIGRTMIN is not actually a signal but a kernel limit. If
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 16 Nov 2003 21:22:54 +0000
Sean Rima
Hi Jerry! On Mon, 17 Nov 2003, Jerry Feldman wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
Does anyone know what this error is
What's the application and what are you doing with it at the time?
Sean
(Forgot about Mutt)
It is a program called Irex which is for BBS/Fidonet use. I have a nasty feeling that because it is a stsic shareware linked program compiled on an old glibc that could be the problem, it is shareware and the source is not available. I would concur. SIGRTMIN is not actually a signal but a kernel limit. If the program is compiled with shared libraries, then it may very will be a binary incompatibility.
I had a feeling, I think it is only when I starts to talk to the net that the problems occur :( Sean
Hi Jerry! On Mon, 17 Nov 2003, Jerry Feldman wrote:
On Sunday 16 November 2003 20:52 pm, Sean Rima wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
Does anyone know what this error is
What's the application and what are you doing with it at the time?
Sean
(Forgot about Mutt)
It is a program called Irex which is for BBS/Fidonet use. I have a nasty feeling that because it is a stsic shareware linked program compiled on an old glibc that could be the problem, it is shareware and the source is not available. I would concur. SIGRTMIN is not actually a signal but a kernel limit. If the program is compiled with shared libraries, then it may very will be a binary incompatibility.
I discoevered that it is something to do with DNS. What is unknown to me but it segfaults or whatever doing a dns checkup. I will have to check with the author but thanks :) Sean
The Sunday 2003-11-16 at 21:22 -0000, Sean Rima wrote:
I have an application that keep dieing with --- SIGRTMIN (Unknown signal 32) @ 0 (0) ---
man 7 signal: Linux supports real-time signals as originally defined in the POSIX.4 real-time extensions (and now included in POSIX 1003.1-2001). Linux supports 32 real-time signals, numbered from 32 (SIGRTMIN) to 63 (SIGRTMAX). (Programs should always refer to real-time signals using notation SIGRTMIN+n, since the range of real-time signal numbers varies across Unices.) Unlike standard signals, real-time signals have no prede fined meanings: the entire set of real-time signals can be used for application-defined purposes. (Note, however, that the LinuxThreads implementation uses the first three real-time signals.) -> The default action for an unhandled real-time signal is to -> terminate the receiving process.
It is a program called Irex which is for BBS/Fidonet use. I have a nasty
Did you ask in the Fidonet international "linux" area? It is quite active. The "linux_bbs" is another possibility.
feeling that because it is a stsic shareware linked program compiled on an old glibc that could be the problem, it is shareware and the source is not available.
I don't know much about Linux programming, but you are having problems with the real-time signal #32 - and the first three signals (ie, 32..34) are reserved for the "LinuxThreads implementation", according to the man above. -- Cheers, Carlos Robinson
participants (7)
-
Carlos E. R. -
Dylan -
Hemond Steve -
Jerry Feldman -
Joe Morris (NTM) -
Richard Bos -
Sean Rima