Okay,
I thought through this again and Martin is right about this point:
Also I can imagine situation when somebody may want to receive all the
install logs to a dedicated logging machine (as is often the case with
logs from production machines) so just a config template or initscript
which logs the IP of log's source would be a better fit.
And here again:
Or maybe a tool which generates the config file, but uses the standard
initscript to start rsyslog with it.
So this is what it's going to be like now:
- my script takes a log_root_path (where all the logs from all the
machines will be stored) and a port
- all it does is generate the config, no rsyslogd running/PID checking etc.
- one daemon + one config is enough for any number of installations: the
logs are stored under log_root_path/installed_machine_IP
- I will ask the rsyslogd maintainer to extend its init script for
running another daemon instance with custom config (generated by
analog). If he says no, I'll take it from there.
Ales
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
