Linuxconf thread. (was Re: The Debian guy again.)
I am forwarding a message I recieved from Jacques Gelinas, the
author/maintainer of Linuxconf. This is for people to hear it directly
from the horses mouth. I have not responded yet, I haven't even digested
the mail fully yet, but this is just to give other people a better feel for
Linuxconf. I have some other mails sitting around which I'll forward to
debian-devel if that is what people want, I think it is the mail archive
though, (is there any way to do a search on Linuxconf on the debian-devel
mail archive?).
Thanks,
Shaya
>Return-Path: <jack@486dos.solucorp.qc.ca>
>X-Authentication-Warning: 486dos.solucorp.qc.ca: jack owned process doing -bs
>Date: Wed, 19 Feb 1997 15:01:45 -0500 (EST)
>From: Jacques Gelinas <jack@solucorp.qc.ca>
>To: Shaya Potter <spotter@itd.nrl.navy.mil>
>Subject: Re: The Debian guy again.
>X-Status: A
>
>This is possible.
>
>linuxconf store configuration information where it belongs when available.
>I mean, /etc/exports is the file manage by linuxconf when configuring NFS.
>There is no official file for firewall configuration or ppp dialout and
>many many others, so linuxconf uses some special files
>(/etc/conf.linuxconf is the major one).
>
>If a standard file exist, linuxconf knows how to parse it. For "unknown"
>package which are managed by linuxconf using its dropin mecanism,
>linuxconf does not store anything about the package, except its state (you
>can enable/disable a package from linuxconf's control panel).
>
>One suggestion though. If you look at a dropin built by linuxconf and your
>proposed "database file", you will find out that the dropin is a super set
>of your idea. Not only it contain the method to start/stop/restart a
>package, but also a method for boot time cleanup, a path to the PID file
>if available, the process name to monitor, the path to all configuration
>files. I am including one dropin here (For the mSql database)
>
> key.name mSQL
> key.revision
> key.desc Mini SQL
> key.startafter
> key.startlevel 0
> key.stoplevel 0
> key.module
> cmd.start /usr/local/Minerva/bin/start
> cmd.stop /usr/local/Minerva/bin/stop
> cmd.reload /usr/local/Minerva/bin/reload
> cmd.boot
> cmd.process msqld
> path.pidfile /var/run/msqld.pid
> key.noreload 0
>
>As you see the format is straight forward and it is possible to generate
>either a sysV init script out of it or create a general purpose sysV init
>script which will look at its name to locate the proper dropin file.
>
>Further, linuxconf provide a user interface to edit/create dropins. This
>will help debian maintainers.It is expect that dropins will evolve in the
>future, containing more information.
>
>For example, a dropin may contain proposed permissions setting for the
>different config files (linuxconf already do many permission check).
>
>New field may be add to point to administration commands. For example, if
>cmd.admin is defined, linuxconf (or any general purpose admin system)
>could lookup the value and fire this script. Another could be cmd.cleanlog
>which will call a script to remove/archive log file.
>
>The general script could look like this
>
>#!/bin/sh
>PKG=`basename $0`
>eval `/usr/sbin/dropin_parse /var/lib/pkg/info/$PKG.database`
>
>if [ "$1" = "start" ] ; then
> $CMD_START
>else [ "$1" = "stop" ] ; then
> $CMD_STOP
>else if [ "$1" = "restart" ] ; then
> $CMD_RESTART
>else if [ "$1" = "admin" ] ; then
> $CMD_ADMIN
>fi
>
>and so on.
>
>Linuxconf could very well look for dropins in /etc/linuxconf/control and
>in /var/lib/pkg/info also.
>
>What do you think ?
>
>
>--------------------------------------------------------
>Jacques Gelinas (jacques@solucorp.qc.ca)
>Linuxconf: The ultimate administration system for Linux.
>see http://www.solucorp.qc.ca/linuxconf
>new development: linuxconf configure dhcpd since 1.9r7
>
>
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: