[no subject]

Jerald M. Sheets jr.
Sr. UNIX Systems Administrator
Datatrac, Inc
770.552.3866 x2494 
*****************
> su -
Password:
# cat /dev/flood > /dev/earth
# rdev noah+beasts
# dd if=noah+beasts of=/dev/earth

 

> -----Original Message-----
&gt; From: ale-bounces at ale.org [<a  rel="nofollow" href="mailto:ale-bounces";>mailto:ale-bounces</a> at ale.org] On 
&gt; Behalf Of Michael D. Hirsch
&gt; Sent: Wednesday, November 17, 2004 9:07 AM
&gt; To: John Mills; Atlanta Linux Enthusiasts
&gt; Subject: Re: [ale] Three d[a]emonic questions
&gt; 
&gt; On Tuesday 16 November 2004 10:51 pm, John Mills wrote:
&gt; &gt; ALErs -
&gt; &gt;
&gt; &gt; I'm doing preliminary debug on a simple server I've written.
&gt; &gt;
&gt; &gt; 1) A few months ago (&lt;=12), someone asked how to set things 
&gt; up so one
&gt; &gt; instance of a service could be kept going, and promptly be 
&gt; restarted when
&gt; &gt; it died or was killed. There were a couple of replies, but 
&gt; I can't refind
&gt; &gt; the thread. Could anyone please remind me where to find this?
&gt; 
&gt; I can't recall exactly, but searching for inittab would be a 
&gt; good start.
&gt; 
&gt; &gt; 2) If I use xinetd to start my server, I need to ensure 
&gt; that, if a running
&gt; &gt; instance of the server exist, that is the one used. If not, 
&gt; a new one
&gt; &gt; should be started. 'man xinetd' suggests this is a 'single_threaded'
&gt; &gt; service. How do I designate a service to be this type?
&gt; 
&gt; I was doing this just last week.  Look at the wait attribute 
&gt; in the man page 
&gt; for xinetd.conf.  This does exactly what you want.
&gt; 
&gt; &gt; 3) My server needs to listen on two ports. I want a 
&gt; connection on either
&gt; &gt; port to use the same, single, running server, or start one 
&gt; if none is
&gt; &gt; running at the moment. Can I achieve this with duplicate entries in
&gt; &gt; /etc/services against the two port numbers? If not, how?
&gt; 
&gt; This I don't know about.  It's easy enough for one server to 
&gt; listen on two 
&gt; ports, but if you are also using xinetd it gets much 
&gt; trickier.  Xinetd would 
&gt; need to know that the two ports are associated, too, and I 
&gt; don't know how to 
&gt; do that.  I can't swear that it isn't possible, however.
&gt; 
&gt; Michael
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00749" href="msg00749.html">[ale] Three d[a]emonic questions</a></strong>
<ul><li><em>From:</em> mhirsch at nubridges.com (Michael D. Hirsch)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00749.html">[ale] Three d[a]emonic questions</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00751.html">[ale] Binary Grep</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00749.html">[ale] Three d[a]emonic questions</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00754.html">[ale] Three d[a]emonic questions</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00750"><strong>Date</strong></a></li>
<li><a href="threads.html#00750"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>