[NCLUG] RedHat Enterprise 3 question

[James Cizek]

  Well I never though of doing it that way!  I actually got it working
  this morning, I had a syntax error in the /etc/xinetd.conf file
  that was hosing up all the services of inetd.  I run sendmail with
  the -bs flag, that is an easy way to get around the port issue
  since -bs lets sendmail read on stdin and output on stdout, you can
  call it inside inetd and put the port you want it to run on in 
  /etc/services.  I just needed to run a seperate sendmail with
  a really high debug level to see why my compare was failing.  
  It had to do with rewriting rule. 

  Thanks for the tip though,  I'll file that one away as "I know 
  I saw how you do this once" memo!  

  Have a great holiday,  -James

  
> 
> Ok James.
> 
> Here's the straight poop on getting a second sendmail running on a 
> different port.
> You'll have to make sure it does what you want.
> 
> Make sure you have the sendmail-cf*.rpm installed.
> 
> cd /etc/mail
> cp sendmail.mc sendmail2.mc
> vi sendmail2.mc
>    Change this line:
>       dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
>    To this:
>       DAEMON_OPTIONS(`Port=4444, Name=MTA')dnl
>     Using whatever port you want it to listen on.
> m4 /usr/share/sendmail-cf/m4/cf.m4 sendmail2.mc >sendmail2.cf
> /usr/sbin/sendmail -bd -C /etc/mail/sendmail2.cf
> 
> Whalla!  You have a sendmail listening on port 4444 although not
> out of xinetd.d.   I guess you can call it without the -bd from xinetd.d
> 
> Bill
> 
> James Cizek wrote:
> 
> >    Bill & group,
> >
> >  OK, checked on the firewall, it's not that.  I know that sendmail
> >  isn't usually started in inetd, my normal sendmail is running
> >  like it should from init, this is a second sendmail that I want
> >  to run in conjunction for a test I need to make.  I went to 
> >  /etc/xinetd.d and copied a script that was already there
> >  (I believe it was the imap script) to a new name, edited it 
> >  to put my new sendmail lines in, removing the imap specific stuff
> >  and changing the enabled = no to enabled = yes
> >  Then I issued service xinetd restart.  It restarted.
> >  I don't know why it shows up in chkconfig --list, I didn't add
> >  anything to /etc/init.d  (and I checked to make sure there wasn't
> >  somethere there called the same thing)
> >
> >  Unless something drastic has changed, I don't believe you put anything
> >  about the port # it runs on in the sendmail.cf.  If you run it out 
> >  of inetd you can put it on any port you want.  I have another sendmail
> >  running on an odd port here to handle listserv delivery stuff without
> >  problem.  That's on AIX but I also have a slackware box running sendmail
> >  on 2 ports (why couldn't they just stick with regular inetd??  It was
> >  so great!!)
> >
> >  So if anyone else has any ideas for me to try, I'm ready to listen!!
> >  This has gotten pretty frustrating since neither Dell nor Redhat 
> >  tech support can figure it out....
> >   Thanks guys!  8-)
> >  -James
> >
> > 
> > James,
> > 
> > Sendmail services are not usually started by xinetd or inetd.  They are 
> > usually run as
> > daemons.  However, this doesn't mean you can't.   When you say that 
> > chkconfig --list
> > shows your new service is set to run on 2 3 4 5 then I know it's not set 
> > up right.  Are
> > you sure you didn't put a script in /etc/init.d for your service?  They 
> > are the only scripts
> > run for different runlevels.
> > 
> > Other things to consider if your sendmail service is running.  Did you 
> > configure your
> > sendmail.cf to listen on a different port than smtp?  Do you have a 
> > firewall that would
> > inhibit you connecting to your port?
> > 
> > Bill
> > 
> > James Cizek wrote:
> > 
> > >  Hi Folks,
> > >
> > >  Having a bit of trouble with RedHat Enterprise server 3. 
> > >  I am used to the old inetd where it was nice and simple
> > >  and you edit one file to make a change.  Since ES uses
> > >  xinetd, I am having trouble starting a new service.
> > >  I have added a new file in my /etc/xinetd.d for the new 
> > >  service (the new service is a sendmail that i want spawned
> > >  at a very high debugging level)  I added the new service
> > >  name and port to /etc/services  I issued 'service xinetd restart'
> > >  and it restarts.  The machine is still refusing connections
> > >  on that new port.  chkconfig --list shows that my new service
> > >  is on and is set to be on at run levels 2 3 4 5
> > >  Am I missing something?  I thought it was so much simpler
> > >  when you just had to edit inetd.conf....   8-)
> > >  
> > >  -James
> > >_______________________________________________
> > >NCLUG mailing list       NCLUG at nclug.org
> > >
> > >To unsubscribe, subscribe, or modify 
> > >your settings, go to: 
> > >http://www.nclug.org/mailman/listinfo/nclug
> > >  
> > >
> > 
> > _______________________________________________
> > NCLUG mailing list       NCLUG at nclug.org
> > 
> > To unsubscribe, subscribe, or modify 
> > your settings, go to: 
> > http://www.nclug.org/mailman/listinfo/nclug
> > 
> > 
> >
> >_______________________________________________
> >NCLUG mailing list       NCLUG at nclug.org
> >
> >To unsubscribe, subscribe, or modify 
> >your settings, go to: 
> >http://www.nclug.org/mailman/listinfo/nclug
> >  
> >
> 
> _______________________________________________
> NCLUG mailing list       NCLUG at nclug.org
> 
> To unsubscribe, subscribe, or modify 
> your settings, go to: 
> http://www.nclug.org/mailman/listinfo/nclug
> 
>