On Fri, Nov 1, 2013 at 1:33 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
> On Fri, Nov 1, 2013 at 2:18 PM, Wes James <comptekki@xxxxxxxxx> wrote:
> > In an earlier thread it was mentioned I could use postfix stop to stop
> > postfix. I'm trying to get sshd started and starting on boot. I did
> > chkconfig sshd on and that worked fine, but then tried sshd start, but
> that
> > didn't work. It looks like I need to do service sshd start (I did just
> > that and it is now started). Why the difference?
>
> 'chkconfig' uses comments in the script in /etc/rc.d/init.d/ as hints
> to make the symlinks in the runlevel directories (/etc/rc.d/rc1.d,
> etc.) for you and some other convenience operations. The runlevel
> directories control what happens at startup and shutdown - based on
> your default runlevel set in /etc/inittab.
>
> 'service' executes the script immediately with the argument you
> provide. If you look at the contents of the script you can see what
> it does with each argument (stop/start/restart are always handled,
> other arguments may be).
>
> --
> Les Mikesell
> lesmikesell@xxxxxxxxx
Thanks. But why do some commands require service service-name command
(like sshd) where postfix works without the service command in front of it?
-wes
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
