Hello,
few days ago, my suse shell account was activated. I installed eggdrop and tried to connect, and was surprised when IRC server showed me that my bot has no active identd. I thought identd was automatic on Polarhome. So I asked my friends who have account on debian and found out that they have running identd without needing any configuration. I tried to install external identd service, but I realised that couldn't work (113 is privileged port, and server wouldn't let it to me) so I have to rely on polarhome's services. 
suse server is quite new one, so I suppose you haven't made the identd working. Is that so, or I am doing something wrong? Are you about to install identd on suse?
I didn't found any such question here in the forum, nor in FAQ
Thanks
			
		

 


 Please try it again. I think the problem was that xinetd failed to start after the server was rebooted several days ago. I have manually started it and identd is now showing up.
 Please try it again. I think the problem was that xinetd failed to start after the server was rebooted several days ago. I have manually started it and identd is now showing up.

 Thanks Sjaz
 Thanks Sjaz