Regarding point 3 – it now gives more information, for example:

“FatController[2025]: Failed to execute command /usr/bin/pytho Error: [2] No such file or directory”

Just committed changes to SVN.

Concerning point 4, I left in support for the -p argument so that old configurations will still work. Although, perhaps it can be taken out now so that was a few versions ago.

Great that you’ve been writing something concerning configuration, would be great to see it – I’ll email you so you can send it to me.

I have few comments:

1. information about bad long option

./fatcontroller –cmd
program prints:
Unrecognised option: -
and I don’t know what option

I suggest, change in file dgetopts.c line 264 on
fprintf(stderr, “Unrecognised option: %s\n”, argv[optind-1]);

2. segmentation fault

./fatcontroller -c t1.sh

and I get
segmentation fault

in non daemon mode you don’t check -l option.

I suggest if no -l option, then set log file to /dev/null.

3. information in syslog

./fatcontroller -c t1.sh -l /dev/null
when t1.sh not exists in syslog i found
Dec 30 16:19:59 hp-ux FatController[8067]: Could not replace child process – shutting down child
in my opinion, this information does not say anything

When program run in daemon mode in syslog i found

Dec 30 17:01:53 hp-ux FatController[8406]: Daemon starting up
Dec 30 17:01:53 hp-ux FatController[8406]: Daemon exiting

program runs with pid=8407, and I know nothing about starting daemon with pid=8407

when I kill the proccess 8407 in syslog is correct information
Dec 30 17:06:54 hp-ux FatController[8407]: Daemon exiting

4. -p –path option

In changelog you write that :
-p –path is deprecated
but still using this option in function parseOptions.

As for suggestions on the program, about which I wrote 28.12.2011 ie, reading options from a configuration file, I have it almost complete.
If you are interested to write.

Best regards
Tom

I suggest adding the option:
–config-file = filename
and read the configuration from a file instead from the command line.
Other options need to test.

Then you can run if needed with the various configuration files:

fatcontroller –config-file = config1
fatcontroller –config-file = config2
fatcontroller –config-file = config3
and so on.

Probably in many cases, only one configuration will be needed, and then run the program without a configuration file ( configuration in /etc/fatcontroller ).

Tom

Thanks for the bug report – I’ve fixed it! As for your suggestion – I’m terrible with bash scripting, but I think what you’re proposing would be possible using a bash script to read the config file and also accept parameters itself. If you fancy giving it a try and get something working then we can add it to the repository. One thing to bear in mind is that people like to be able to have several different configuration files and specify which one to use when calling fatcontrollerd.

Generally I agree – the focus for the next release should be configuration in general – how it is configured and how it checks those parameters before startup.

I found another little bug:

–debug option don’t writes information about name of error log file.

I have a suggestion:

Currently, to run program I have to give many options or use script fatcontrollerd and configuration file fatcontroller.

I propose that ( shortly ):

move the options to the standard configuration file ( default /etc/fatcontroller )

leave only command line options:

-f –config-file ( configuration in another file )
–help
–debug
–test-fire
–nodaemonise ( same as daemon = 0 in configuration file, useful to run without daemon )

read setup from a configuration file.

To run :
/usr/local/bin/fatcontroller

To view configuration :
/usr/local/bin/fatcontroller –test-fire

To run without demonise:
/usr/local/bin/fatcontroller –nodemonise

For me it will be easier.

What do you think about it?.
Maybe in the next version?

Tom