ITEM: F1177L

How to configure the POP daemon for startup by the inetd Super Daemon?


QUESTION:

I am installing POP on all of my UNIX systems, and wanted to know what
I need to do in AIX.  POP (Post Office Protocol) pushes mail between
machines.  For example, I can check my mail on my PC without having to
log onto the RISC machine.

I got POP Version 3 source code from the Internet.  I put it on my RISC/6000
and it compiled fine (no errors).  My question is how, exactly, do I implement
it on the RISC?  I have done this on HP and Ultrix with no problem, but the
RISC is a little different because of the ODM.

Based on my experiences and RFC 1081 (POP V 3), I think I need to
  - add a line for socket 110 to the /etc/services file.
  - add a line to /etc/inetd.conf       
  - kill the inetd
  - restart inetd and the popd will be added in.

Is this correct?  Should I do this via SMIT?  If so, how?"

Response:

You can do this via command line or through SMIT.  I will outline both methods:

       COMMAND LINE                            VIA SMIT

1. edit /etc/services                      type "smit inetserv"
   add line for socket 110                 Choose "Add a Service"

2. edit /etc/inetd.conf                    type "smit chinetdconf"
   add a line for popd                     Choose "Add an inetd Subserver"

3.     \<---------- execute the command "inetimp" ------------>                                               
   (This command is key! it syncs up the ODM and the inetd.conf file.)
 4.     \<------ execute the command "refresh -s inetd" ------->
   (This restarts inetd and incorporates your new service.)

I believe there are ways to do steps 3 and 4 via SMIT, but the command line
version is easy to type and straightforward.  The benefit of doing steps 1 and 2
via SMIT is that it worries about the format of the file entry and, thus, the
chance of error is eliminated.


Support Line: How to configure the POP daemon for startup by the inetd Super Daemon? ITEM: F1177L
Dated: November 1993 Category: N/A
This HTML file was generated 99/06/24~13:30:52
Comments or suggestions? Contact us