I have a new installation of 9.2, but cannot start xinetd either from the command line or via yast2. I didn't have this problem with 9.1 I'd appreciate suggestions. Thanks, - Richard -- Richard Kimber http://www.psr.keele.ac.uk/
On Saturday 12 February 2005 11:10 am, rkimber@ntlworld.com wrote:
I have a new installation of 9.2, but cannot start xinetd either from the command line or via yast2. I didn't have this problem with 9.1
I'd appreciate suggestions.
Error messages (when trying the console start) ??
On Sat, 12 Feb 2005 12:55:39 -0500
Bruce Marshall
On Saturday 12 February 2005 11:10 am, rkimber@ntlworld.com wrote:
I have a new installation of 9.2, but cannot start xinetd either from the command line or via yast2. I didn't have this problem with 9.1
I'd appreciate suggestions.
Error messages (when trying the console start) ??
"Failed" -Richard -- Richard Kimber http://www.psr.keele.ac.uk/
On Saturday 12 February 2005 06:01 pm, rkimber@ntlworld.com wrote:
On Sat, 12 Feb 2005 12:55:39 -0500
Bruce Marshall
wrote: On Saturday 12 February 2005 11:10 am, rkimber@ntlworld.com wrote:
I have a new installation of 9.2, but cannot start xinetd either from the command line or via yast2. I didn't have this problem with 9.1
I'd appreciate suggestions.
Error messages (when trying the console start) ??
"Failed"
What messages do you get in /var/log/messages at the time of the failure? What does /usr/sbin/xinetd give you for error messages?
-Richard -- Richard Kimber http://www.psr.keele.ac.uk/
On Sat, 12 Feb 2005 18:25:53 -0500
Bruce Marshall
On Saturday 12 February 2005 06:01 pm, rkimber@ntlworld.com wrote:
On Sat, 12 Feb 2005 12:55:39 -0500
Bruce Marshall
wrote: On Saturday 12 February 2005 11:10 am, rkimber@ntlworld.com wrote:
I have a new installation of 9.2, but cannot start xinetd either from the command line or via yast2. I didn't have this problem with 9.1
I'd appreciate suggestions.
Error messages (when trying the console start) ??
"Failed"
What messages do you get in /var/log/messages at the time of the failure?
What does /usr/sbin/xinetd give you for error messages?
It turned out that there was something in a configuration file for a service that I wasn't using that xinetd objected to, and it was exiting when it encountered it. Simply removing the file from xinetd.d solved it. That seems rather poor program design to me. I should have thought a better approach would be for xinetd not to make that particular service available and to start with the validly configured services, rather than just giving up altogether. - Richard. -- Richard Kimber http://www.psr.keele.ac.uk/
On Monday 14 February 2005 07:16 am, rkimber@ntlworld.com wrote:
It turned out that there was something in a configuration file for a service that I wasn't using that xinetd objected to, and it was exiting when it encountered it. Simply removing the file from xinetd.d solved it.
That seems rather poor program design to me. I should have thought a better approach would be for xinetd not to make that particular service available and to start with the validly configured services, rather than just giving up altogether.
And leave you thinking that everything was fine even though a (maybe) important process wasn't working??? That's not the way I want it...
The Monday 2005-02-14 at 11:33 -0500, Bruce Marshall wrote:
That seems rather poor program design to me. I should have thought a better approach would be for xinetd not to make that particular service available and to start with the validly configured services, rather than just giving up altogether.
And leave you thinking that everything was fine even though a (maybe) important process wasn't working??? That's not the way I want it...
On a headless machine, you could be left out, and be prevented from solving the problem reometely. -- Cheers, Carlos Robinson
On Mon, 14 Feb 2005 11:33:18 -0500
Bruce Marshall
That seems rather poor program design to me. I should have thought a better approach would be for xinetd not to make that particular service available and to start with the validly configured services, rather than just giving up altogether.
And leave you thinking that everything was fine even though a (maybe) important process wasn't working??? That's not the way I want it...
But it wouldn't leave me thinking that, since the wrongly configured service wouldn't work, but the others would. If I needed the wrongly configured service I would find out why it wasn't working. If I didn't need it ..... - Richard. -- Richard Kimber http://www.psr.keele.ac.uk/
participants (3)
-
Bruce Marshall
-
Carlos E. R.
-
rkimber@ntlworld.com