Re: (Clarification) Installation Quesiton on Qmail. init.d directory and qmail script file.

1999-09-19 Thread Rick Myers

On Sep 19, 1999 at 03:09:18 -0500, Mark Thomas twiddled the keys to say:
> Would it be appropriate to add the:
> "qmail start"  somewhere in the rc.local script (bottom section of file)? 

That would work, but the proper place is in rc.M just below where you
comment out the original sendmail startup.

> "qmail stop"   somewhere in the rc.0 or rc.6 local script (top section)?

That would go in rc.6, and again in rc.K, both at the top before the
original script kills all processes. (BTW, rc.0 should already be a
symlink to rc.6.)

> ALSO:
> Creating links at the bottom of 2.8.2:
> ln -s ../init.d/qmail RCDIR/rc0.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc1.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc2.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc3.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc4.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc5.d/K30qmail
> ln -s ../init.d/qmail RCDIR/rc6.d/K30qmail

This is for the new style init. I doubt seriously you get anything but
error messages if you attempt this.

> With Slackware:
> ln -s /etc/rc.d/qmail /etc/rc.d/rc.0(K30qmail)
> rc.0,4,6,K,N, and S are files. 
> Do I need to manually enter some data in the rc.? files, or create some files in a 
>location for the links?

Edit as mentioned above. Forget the symlink, it'll break your shutdown.

> darkstar:/etc/rc.d# 

You should give your system it's own hostname. ;-)

Rick Myers[EMAIL PROTECTED]

The Feynman Problem   1) Write down the problem.
Solving Algorithm 2) Think real hard.
  3) Write down the answer.



RE:(Clarification) Installation Quesiton on Qmail. init.d directory and qmail script file.

1999-09-19 Thread Mark Thomas

Thanks for your reply, you are correct at all points.
We all appreciate the time you guys spend documenting these things for the
community. I chose your document because I have little or no Linux
experience (1Week), and the INSTALL and FAQ documents were a bit above my
head.  Thanks for your HOWTO!
I have included some info on my Slackware file structure. It may help
clarify the document for Slackware users. qmail-start-stop-script.txt and
support files of the /etc/rc.d directory.  rc.local-Startup file  and
rc.0-stop script.
I also have some issues with the links, since the rc.? are files and not
directories.
I appreciate your help.
Mark Thomas.

See Below: ((

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Dave Sill
Sent: Saturday, September 18, 1999 1:27 PM
To: [EMAIL PROTECTED]
Cc: Mark Thomas
Subject: Re: Installation Quesiton on Qmail. init.d directory and qmail
script file.

Mark Thomas <[EMAIL PROTECTED]> wrote:
>
> I). I am installing qmail 1.03 from Dave Sill's "Life with Qmail" dated
July
> 21, 1999.  I am in section # 2.8.2 System Startup Files, and it says to
> install a script file I just created "qmail" to launch qmail at boot into
my
> init.d directory.
> The document says it should be in one of the following locations:
> /etc/init.d
> /etc/rc.d/init.d
> /sbin/init.d
> I have no such directory on my system. (Slackware 3.6)

LWQ says "should" because it's impossible to cover every possibility.
((  I attached a text file with info about the rc.d directory
(( structure on Slackware.  Please review!

> It appears that Slackware uses /etc/rc.d for the initialization files.  I
> think the qmail script file that will start qmail on boot should be
located
> here? Can anyone verify this for me?
What's the structure of /etc/rc.d? What subdirectories does it have?
(( Structure included in the text file with info from above.

> setuser (qmaill) cyclog /var/log/qmail & ** Is
> qmaill a typo, or variable of somekind?
qmaill is a user (in /etc/passwd) which you should have set up in 2.5.4.
((  Yes, it was. I cut and pasted the text and didn't notice the
extra (( character, in qmail(l)

> setuser qmaill cyclog /var/log/qmail/(smtpd &) ***
> I have a qmail-smtpd file here.
Are you sure about that? LWQ certainly doesn't create a qmail-smtpd file
under /var/log/qmail.
(( Right again-> I guess I was just about frazzeled here! 

It's probably a good idea to read through the entire Installation section
before attempting one's first installation. I'll add a note to that effect.

((  All except whats left could have been answered if I
((  would have read the entire section prior to the sections
install.
((  MarkT.


 inittab
 rc.0
 rc.local

**
Would it be appropriate to add the:
"qmail start"  somewhere in the rc.local script (bottom section of file)? 
"qmail stop"   somewhere in the rc.0 or rc.6 local script (top section)?
ALSO:
Creating links at the bottom of 2.8.2:
ln -s ../init.d/qmail RCDIR/rc0.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc1.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc2.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc3.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc4.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc5.d/K30qmail
ln -s ../init.d/qmail RCDIR/rc6.d/K30qmail

With Slackware:
ln -s /etc/rc.d/qmail /etc/rc.d/rc.0(K30qmail)
rc.0,4,6,K,N, and S are files. 
Do I need to manually enter some data in the rc.? files, or create some files in a 
location for the links?
***

If Sendmail is currently installed, running the command 
"find RCDIR -name "*sendmail" -print" will give you numbers 
that should work for your system. 
I tried this also, the only files I have on my system that fit the 
*sendmail criteria was sendmail, setup.sendmail and REMOVE.sendmail.

**I received this reply from my previous post.  It gives some info on Slackware.

Slackware doesn't use the System V-style init scripts that this
documentation refers to.  Slackware uses old-style /etc/rc.d scripts.

What this probably means is that you need to stick your qmail start/stop script 
somewhere else, then manually edit by hand the various scripts in /etc/rc.d to run the 
qmail start/stop script.  
Going from memory, /etc/rc.d/rc.local would be a good place to stick in the start 
script.  
I think /etc/rc.d/rc.shutdown would be a good place to stick in the stop script, to 
bring the system down during system shutdown.

In any case, you should read the contents of your /etc/inittab to see
which /etc/rc.d scripts get invoked at which time.  Then make ap