Re^4: Address Bind issue reincarnation

Hi almut,

I wished to use xinetd first, but since my server code i wrote is using socket functions, so the communication is not through stdin/stdout which brings me to the 'Address bind' issue

I am trying another approach of making a standalone daemon. The goal is to make a server daemon listening to a port continuously.

I read the links you sent me, thanks a lot. I am thinking now to make a script in /etc/init.d/ and define a run level for it. What do you say?

Comment on Re^4: Address Bind issue reincarnation

Replies are listed 'Best First'.
Re^5: Address Bind issue reincarnation by almut (Canon) on Jul 19, 2010 at 09:38 UTC
I am thinking now to make a script in /etc/init.d/ and define a run level for it. Sounds like a good plan :) (in case you don't want to use `daemontools` for some reason, that is) See runlevel if you need ideas on which one to choose.	[reply] [d/l]
Re^6: Address Bind issue reincarnation by sajanagr (Acolyte) on Jul 19, 2010 at 11:21 UTC
Hi almut, I wanted to have a proper control of my server code to stop and start the server daemon. Using daemontools, I came to know that I can keep my command in rc.local, but that is no better control of the daemon as per my understanding. I made a script in init.d to start, stop, restart and to check the status of my daemon. It would had been great if I could had used xinetd, but this is a lightweighted code anywayz. thanks for the support	[reply]
Re^7: Address Bind issue reincarnation by afoken (Chancellor) on Jul 19, 2010 at 12:00 UTC
Ummm, start reading the daemontools documentation. You may also want to read a more "human readable" intro to daemontools. daemontools and rc.local are VERY different. The only thing they have in common is that you usually use a shell script to start your daemon. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]