[Slackbuilds-users] Suggestion for packages which require a startup file.
chaos.proton at gmail.com
Sun Jun 20 12:38:32 UTC 2010
On Sun, Jun 20, 2010 at 7:44 PM, Robert Kelsen <rkelsen at optusnet.com.au> wrote:
> The proposed resolution to this issue:
> A simple symlink.
> Yes, a symlink (or series of symlinks). It can be included as part of the
> package, and is removed if a package is uninstalled.
> Using our TiMidity++ example above, the symlink would point to
> /etc/rc.d/rc.timidity and be located under /etc/rc.d/rc4.d. You could
> call it S99timidity or something similar. I chose rc4.d, because it
> makes sense that someone needing TiMidity++ would mainly use it in that
> runlevel. It is a CLI-based tool, so you could add it to other runlevels
I think one negative reason not to use it is that it is _possible_
that you start the service twice. For example, a user see the script
in rc.d, and he knows that Slackware use BSD style init, so he add
something like "/etc/rc.d/rc.timidity start" in rc.local without
knowing that it is already started by the SystemV init compatible
layer. So I think if a package mean to use SystemV style init, please
drop the startup script into /etc/init.d/(which is a symlink to
/etc/rc.d/init.d) and then symlink it to /etc/rc[0-6].d. I think the
folder name says that "all the scripts under me are intended to be
SystemV style init scripts." Anyway, my statement is not official at
But the positive reason to use your solution is that it is simple to
end-user. Install and reboot(or manually do a startup), that's all. No
need to edit files after install and uninstall.
More information about the SlackBuilds-users