"Cron" is a daemon . You can download its sources and have a look at it . --- Preetham D Naik <pdn@sasken.com> wrote: > i know that but what i wanted is to know how the > daemon process is > internally implemented. I wanted its source code.I > know how to make a > process a daemon. > Thank you > rgrds > > "Amit Limaye" <amit.limaye@patni.com> wrote in > message > 06af01c3f1fb$43143930$0d0ba8c0@patni.com">news:06af01c3f1fb$43143930$0d0ba8c0@patni.com... > > Hey Preetham > > Read Unix Network Programming - Richard > Stevens > > or Adavanced Programming in the Unix Evironment - > Richard Stevens > > U will find Sample daemon code there > > > > -SIGTERM > > amit > > > > ----- Original Message ----- > > From: "Preetham D Naik" <pdn@sasken.com> > > To: <kernelnewbies@nl.linux.org> > > Sent: Friday, February 13, 2004 10:50 AM > > Subject: implementation of daemon process > > > > > > > hi, > > > where can i find the implementation of > the daemon process. I > want > > to > > > customize it to my own needs. > > > Thank you > > > Rgrds > > > > > > > > > > > > > -------------------------------------------------------------------------- > -- > > ---- > > > > > > > > *********************************************************************** > > > > > > PLEASE VISIT US AT STAND E13B, AT 3GSM WORLD > CONGRESS 2004, CANNES. > > > > > > > ******************************************************************** > > > > > > SASKEN BUSINESS DISCLAIMER > > > > > > This message may contain confidential, > proprietary or legally Privileged > > information. In case you are not the original > intended Recipient of the > > message, you must not, directly or indirectly, > use, Disclose, distribute, > > print, or copy any part of this message and you > are requested to delete it > > and inform the sender. Any views expressed in this > message are those of > the > > individual sender unless otherwise stated. Nothing > contained in this > message > > shall be construed as an offer or acceptance of > any offer by Sasken > > Communication Technologies Limited ("Sasken") > unless sent with that > express > > intent and with due authority of Sasken. Sasken > has taken enough > precautions > > to prevent the spread of viruses. However the > company accepts no liability > > for any damage caused by any virus transmitted by > this email. > > > > > > > *********************************************************************** > > > > > > > > > -- > > Kernelnewbies: Help each other learn about the > Linux kernel. > > Archive: > http://mail.nl.linux.org/kernelnewbies/ > > FAQ: http://kernelnewbies.org/faq/ > > > > > *********************************************************************** > > PLEASE VISIT US AT STAND E13B, AT 3GSM WORLD > CONGRESS 2004, CANNES. > > ******************************************************************** > > SASKEN BUSINESS DISCLAIMER > > This message may contain confidential, proprietary > or legally Privileged information. In case you are > not the original intended Recipient of the message, > you must not, directly or indirectly, use, Disclose, > distribute, print, or copy any part of this message > and you are requested to delete it and inform the > sender. Any views expressed in this message are > those of the individual sender unless otherwise > stated. Nothing contained in this message shall be > construed as an offer or acceptance of any offer by > Sasken Communication Technologies Limited ("Sasken") > unless sent with that express intent and with due > authority of Sasken. Sasken has taken enough > precautions to prevent the spread of viruses. > However the company accepts no liability for any > damage caused by any virus transmitted by this > email. > > *********************************************************************** > ________________________________________________________________________ Yahoo! India Education Special: Study in the UK now. Go to http://in.specials.yahoo.com/index1.html -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
