Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general? - Once I have the latest threads::shared in buildable SRPM is there an interest in picking that up, or is there anyone that would like to put it in a repository?
Cheers...james
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general?
- Once I have the latest threads::shared in buildable SRPM is there
an interest in picking that up, or is there anyone that would like to put it in a repository?
Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
The test that is failing is the t/op/pwent test. I'll be looking at why its failing, but the same questions still apply.
Thanks...james
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general?
- Once I have the latest threads::shared in buildable SRPM is there
an interest in picking that up, or is there anyone that would like to put it in a repository?
Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
The test that is failing is the t/op/pwent test. I'll be looking at why its failing, but the same questions still apply.
OK, hre is the test error:
1..2 # where NIS passwd # max = 25, n = 14, perfect = 0 # # The failure of op/pwent test is not necessarily serious. # It may fail due to local password administration conventions. # If you are for example using both NIS and local passwords, # test failure is possible. Any distributed password scheme # can cause such failures. # # What the pwent test is doing is that it compares the 26 first # entries of NIS passwd # with the results of getpwuid() and getpwnam() call. If it finds no # matches at all, it suspects something is wrong. # not ok 1 # (not necessarily serious: run t/op/pwent.t by itself) ok 2
So that on is not anyone's problem, save that I have to figure out how to get it to not die...but the situation it reports that would make it not a real bug is the situation on that build server.
Anyway, once I have the thing building with the non-leaky thread::shared(3pm) libs, does anyone want to the SRPM (i.e. to host it).
Cheers...james
Anyway, once I have the thing building with the non-leaky thread::shared(3pm) libs, does anyone want to the SRPM (i.e. to host it).
Have you tried the perl in centosplus (from RHWAS)?
James Olin Oden wrote:
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general?
- Once I have the latest threads::shared in buildable SRPM is there
an interest in picking that up, or is there anyone that would like to put it in a repository?
Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
The test that is failing is the t/op/pwent test. I'll be looking at why its failing, but the same questions still apply.
Is this something that is already fixed in the centosplus 5.8.8 version? Maybe you can just enable the repository and use yum to update perl (and httpd if you want a working mod_perl).
On 3/9/07, Les Mikesell lesmikesell@gmail.com wrote:
James Olin Oden wrote:
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general?
- Once I have the latest threads::shared in buildable SRPM is there
an interest in picking that up, or is there anyone that would like to put it in a repository?
Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
The test that is failing is the t/op/pwent test. I'll be looking at why its failing, but the same questions still apply.
Is this something that is already fixed in the centosplus 5.8.8 version? Maybe you can just enable the repository and use yum to update perl (and httpd if you want a working mod_perl).
Hmmm...ignorant me did not know of CentOS plus. I'll check and let you find out. I'm glad I sent the email, no matter how embarasing. I'll let you know if the fixed threads::shared library is in it.
Thanks...james
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
On 3/9/07, Les Mikesell lesmikesell@gmail.com wrote:
James Olin Oden wrote:
On 3/9/07, James Olin Oden james.oden@gmail.com wrote:
Hi All,
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it. When I try to build it some of the tests its running fail (failure went off my screen but I'll have that in a moment) and it failed to build. BTW, I'm building on a CentOS 4.2 system.
So my questions are two fold:
- Does anyone know of any known issues with building the perl SRPM in general?
- Once I have the latest threads::shared in buildable SRPM is there
an interest in picking that up, or is there anyone that would like to put it in a repository?
Correction I'm building on CentOS 4.3 and I pulled the SRPM from CentOS 4.4.
The test that is failing is the t/op/pwent test. I'll be looking at why its failing, but the same questions still apply.
Is this something that is already fixed in the centosplus 5.8.8 version? Maybe you can just enable the repository and use yum to update perl (and httpd if you want a working mod_perl).
Hmmm...ignorant me did not know of CentOS plus. I'll check and let you find out. I'm glad I sent the email, no matter how embarasing. I'll let you know if the fixed threads::shared library is in it.
Its using the same broken leaky version of threads::shared(3pm).
Cheers...james
On 3/9/07, Charlie Brady charlieb-centos-devel@budge.apana.org.au wrote:
On Fri, 9 Mar 2007, James Olin Oden wrote:
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it.
Please make sure the RedHat's bugzilla is aware of the problem.
Sure...I'll see if I can make a simpler reproducer. It seems like when you write something threads in any language simple goes out the door.
Cheers...james
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Fri, 9 Mar 2007, James Olin Oden wrote:
On 3/9/07, Charlie Brady charlieb-centos-devel@budge.apana.org.au wrote:
On Fri, 9 Mar 2007, James Olin Oden wrote:
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it.
Please make sure the RedHat's bugzilla is aware of the problem.
Sure...I'll see if I can make a simpler reproducer. It seems like when you write something threads in any language simple goes out the door.
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Charlie Brady wrote:
Please make sure the RedHat's bugzilla is aware of the problem.
Sure...I'll see if I can make a simpler reproducer. It seems like when you write something threads in any language simple goes out the door.
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Yes, but that person probably didn't have a multi-(hyperthreaded) processor computer dedicated to a single task when he said that. Or more than 1024 file descriptors open for that matter.
Sure...I'll see if I can make a simpler reproducer. It seems like when you write something threads in any language simple goes out the door.
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Maybe you're thinking of (the famous) Alan Cox's (famous) statement:
"A computer is a state machine. Threads are for people who cant program state machines."
http://lkml.org/lkml/2000/1/22/172
Sorry for offtopicness, -Ed
On 3/9/07, Charlie Brady charlieb-centos-devel@budge.apana.org.au wrote:
On Fri, 9 Mar 2007, James Olin Oden wrote:
On 3/9/07, Charlie Brady charlieb-centos-devel@budge.apana.org.au wrote:
On Fri, 9 Mar 2007, James Olin Oden wrote:
I'm trying to rebuild the version of perl that is in CentOS 4.3 to update the version of threads::shared(3pm) that has a serious memory leak in it.
Please make sure the RedHat's bugzilla is aware of the problem.
Sure...I'll see if I can make a simpler reproducer. It seems like when you write something threads in any language simple goes out the door.
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Funny you should say that. The original design of this daemon was to use select with mulitple processes connected with pipes. I actually know how to do that but at some point as an alternative I started looking at perl threads, and it looked like it would simplify things. I think in the end it did somewhat, but instead of pipes you have fifos to communicate between the master thread and the listener threads...sounds pretty isomorphic to me. Furthermore, I still have to serialize objects going into the fifo because perl does not support just sending an object through the fifo...guess what...I would have had to do that with pipes and select().
Cheers...james
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
James Olin Oden wrote:
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Funny you should say that. The original design of this daemon was to use select with mulitple processes connected with pipes. I actually know how to do that but at some point as an alternative I started looking at perl threads, and it looked like it would simplify things. I think in the end it did somewhat, but instead of pipes you have fifos to communicate between the master thread and the listener threads...sounds pretty isomorphic to me. Furthermore, I still have to serialize objects going into the fifo because perl does not support just sending an object through the fifo...guess what...I would have had to do that with pipes and select().
Wouldn't separate processes using a shared memory segment have been easier all around? I think you still have to serialize in and out because of perl's strange way of storing variables, though.
On 3/10/07, Les Mikesell lesmikesell@gmail.com wrote:
James Olin Oden wrote:
Yep. Didn't someone famous once say that threads is for those who can't work out how to use select()?
Funny you should say that. The original design of this daemon was to use select with mulitple processes connected with pipes. I actually know how to do that but at some point as an alternative I started looking at perl threads, and it looked like it would simplify things. I think in the end it did somewhat, but instead of pipes you have fifos to communicate between the master thread and the listener threads...sounds pretty isomorphic to me. Furthermore, I still have to serialize objects going into the fifo because perl does not support just sending an object through the fifo...guess what...I would have had to do that with pipes and select().
Wouldn't separate processes using a shared memory segment have been easier all around? I think you still have to serialize in and out because of perl's strange way of storing variables, though.
Ahhh, but I never quite got SysV IPC down in perl, though select was fine (-;
Actually what led me to believe that threads would be easier was that shared data is supported. Unfortunatey, shared objects are not. Really shared references are not supported.
But my app works fine and is fairly maintable, provided the stinking memory leak in the threads::shared library is gone (-:
Cheers...james
-- Les Mikesell lesmikesell@gmail.com
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
-
Charlie Brady -
Ed Price -
James Olin Oden -
Jim Perrin -
Les Mikesell