This is an apparent bug?! As those "random" ports should not be < 1024? only high numbered ports should be random? or the rpc based services should be confined in some range. IMO if this is causing services to fail to start, it is a serious bug!
On 8/21/07, Trond Eivind Glomsrød <[EMAIL PROTECTED]> wrote: > > > On Aug 21, 2007, at 12:57 AM, Ahmed Kamal wrote: > > Hi, > I'am seeing an issue with RHEL5.0 where some service (I only remember > statd) would listen on port 631, preventing cupsd from starting! Has anyone > seen something like this? My temp work-around has been to move the cups > service to start much earlier than anything else > > > This happens every now and then, as some services don't use hardcoded > ports but just takes an available port and tells portmap about it.... > > > -- > Trond Eivind Glomsrød > Product Development Manager > Scali - www.scali.com > Higher Performance Computing > > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list > >
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
