Re: [Smartmontools-support]About the makefile

[Bruce A. <ba...@gr...>]

Hi Erik,

> In particular, a few lines under "make install".
> 
>         install -m 755 -o root -g root -D smartd.initd
> $(DESTDIR)/etc/rc.d/init.d/smartd
> 
> ... I don't want this. I'm on a Slackware system, which has smartd
> integrated in other ways in the startup files. No /etc/rc.d/init.d/
> hierarchy, except for compatibility. In general, changing/adding startup
> files on make install seems a little unprofessional, it should rather be
> the province of binary package maintainers. Put smartd.initd in
> /usr/share/doc as an example instead?

I did this; I didn't realize that having startup scripts in
/etc/rc.d/init.d was non-standard.

One bit of "good" news.  Just putting the script there does not of course
cause the service to be started (at any runlevel). So in this sense I
(we??) are not being unprofessional. The only thing that causes it to
start/end is if there is a symbolic link to it from the appropriate S* or
K* entry in the appropriate runlevel directory.  And that's what the
chkconfig command does: it creates the link for runlevels 3 and 5. Unless
the user gives that command, no link is created, and no service is
started.

>         @echo -e "\n\nTo manually start smartd on bootup, run
> /etc/rc.d/init.d/smartd start"
>         @echo "To automatically start smartd on bootup, run
> /sbin/chkconfig --add smartd"
> 
> What's chkconfig? A suse thing? It is not on my system...

It's a utility that installs the links.

> Suggestions / disagreements?

I'd be happy for you to fix it, provided that there is a "make" target
that will install the init file in the correct place for Redhat systems,
and that you modify the documentation (index.html, README, smartd.8) to
keep it consistent.

Thus the invokation might be:
 make
 make install (binaries, documentation)
 make install-redhat-init (install init scripts for redhat system)
But I'm not sure if this would generalize nicely to Slackware, SuSE and
other systems.

Comments?

Bruce