14 Feb
2005
14 Feb
'05
16:33
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...