<div>
1) What happened if I used TCP and Dgram combination? Will the daemon runs?<br />
2) &nbsp;service name<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; socket type<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; protocol<br />
Suppose that if the socket type is raw/sequence packet ..... what should be the protocol? As far as I am concerned the value for protocol is limited to TCP/UDP/RPC/Unix?<br />

</div>


1) What happened if I used TCP and Dgram combination? Will the daemon runs?
2)  service name
         socket type
         protocol
Suppose that if the socket type is raw/sequence packet ..... what should be the protocol? As far as I am concerned the value for protocol is limited to TCP/UDP/RPC/Unix?


<div>
<div class="content wysiwyg-content">
in inetd.conf , they are stream/dgram parameter, <br />
<br />
usually stream is refering to TCP ? <br />
but then is it possible to have stream with UDP as a parameter of service?<br />
If not, why they need to mention whether stream/dgram why not directly called it TCP or UDP?<br />

</div>
</div>


in inetd.conf , they are stream/dgram parameter, 

usually stream is refering to TCP ? 
but then is it possible to have stream with UDP as a parameter of service?
If not, why they need to mention whether stream/dgram why not directly called it TCP or UDP?


/etc/inetd.conf stream TCP

Operating systems perform basic tasks, such as recognizing input from the keyboard, sending output to the display screen, keeping track of files and directories on the disk, and controlling peripheral devices such as disk drives and printers. For large systems, the operating system makes sure that different programs and users running at the same time do not interfere with each other. The operating system is also responsible for security, ensuring that unauthorized users do not access the system. Operating systems provide a software platform on top of which other programs, called application programs, can run.