Helmut Drodofsky writes: > see > http://lists.centos.org/pipermail/centos/2013-July/135847.html > > I have had the same problem and I will never understand, why this is > unchanged up to now. Excellent, thanks! Now I know how to work around it. I've seen this happening before, on CentOS5, when cups would sometimes not start. Upstream knows this problem very well or they wouldn't have introduced portreserve(1). Pretty hilarious they can't fix the actual problem. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: CentOS6 xinetd failure
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: centos@xxxxxxxxxx
- Subject: Re: CentOS6 xinetd failure
- From: Lars Hecking <lhecking@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 Dec 2013 15:22:05 +0000
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <52A71F1A.9020401@internet-xs.de>
- Mail-followup-to: centos@xxxxxxxxxx
- User-agent: Mutt/1.5.21 (2010-09-15)
- References:
- CentOS6 xinetd failure
- From: Lars Hecking
- Re: CentOS6 xinetd failure
- From: Helmut Drodofsky
- CentOS6 xinetd failure
- Prev by Date: Re: Centos6.5 Intel Corporation Centrino Advanced-N 6235 not working
- Next by Date: Re: about C program of CPP macro problems
- Previous by thread: Re: CentOS6 xinetd failure
- Next by thread: CentOS-announce Digest, Vol 106, Issue 5
- Index(es):
 |