Manuel Arostegui Ramirez escribió:
El Viernes, 29 de Junio de 2007 16:32, Enrique Verdes escribió:
  
I'd like some features in the linux agents, like having the modules out
of the pandora_agent.conf, and into an /etc/pandora/modules/ directory,
where each module can have its own file, like pam.d or xinetd.d I think
this way upgrading can be more easy. Also, I'd like to have a
module_enabled attribute, in order to get the desired modules working. I
can work on the agent, because I feel very comfortable working on bash.
Can't promise I will do it fast, but maybe next week I can have it
working. Tell me how I can send the agent code to you. I won't break the
server, because the module_enabled will tell the agent if it has to
include module info at the xml data file.

I'd like to ease the modules administration in the pandora agents, so
I'm thinking about some ways to do it.

Tell me what do you think about this idea.

Regards...
    


Well, I don't see the point in all of this stuff.
I mean, by now, pandorafms it's not easy to install and set up succesfull, 
that's the truth don't mind whether you like it or not.
In my opinion having another dir and another files would be, more likely, 
worse, at least for now. It will make everybody get confused about how the 
hell to configure pandorafms, either server or agent.

What happened with apache2 and the modules? As you guys now all the modules in 
apache 1.3 version were in the apache2.conf or httpd.conf, it depends on the 
distro, and in the second version of the apache they decided to use 
mod-available to place all the modules and then mod-enable which contains "ln 
-s" files to the previus mod-available ones, is that user friendly, IMHO, no.
It is much more simplier to have only one file. 
And it seems to me that you propossed something similar with pandora agents, 
don't you?

Anyways, we'll see what happen and see what the other members of the proyect 
think about this :-)

Cheers

  
Well, Manuel, I'm a quite new user of Pandora, and can see it has it's issues to install and configure, but from 1.2 to this 1.3 beta I'm trying I can see it's getting better about it.
About the agent configuration, I wasn't thinking about apache, but about pam.d, xinetd.d or yum.repos.d instead. In those cases you include a directory and all the files in the directory gets evaluated to enable or disable services. This doesn't prevent you from having a unique config file, but, as you add more modules, or disable existing ones, I think having the choice to put the modules in a directory whith one file per module can ease the management.

Anyway, I like to hear different ideas and opinions. That's what I love about open source development model. Thanks for reading my suggestions and take the time to answer.

Regards.
--
------------------------------------------------------------------------------------------------------------------
    Enrique Verdes

UyGroup
Consulting & Technology

www.uygroup.com.uy

Av. Gral. Paz 1481 - CP 11400
Montevideo - Uruguay
Phone/Fax: (+598-2) 600-6200 - ext. 223

------------------------------------------------------------------------------------------------------------------
AVISO DE CONFIDENCIALIDAD:
LA INFORMACIÓN CONTENIDA EN ESTE CORREO ELECTRÓNICO ES PRIVILEGIADA Y CONFIDENCIAL Y FUE ENVIADO PARA EL USO EXCLUSIVO DEL DESTINATARIO DESIGNADO EN EL MISMO.
Si usted no es el destinatario, se prohibe estrictamente la reproducción, distribución, y cualquier otra forma de difusión o uso de esta comunicación.
Si usted ha recibido este correo electrónico por error, por favor contéctese con nosotros inmediatamente al teléfono: (+598-2) 600-62-00 o por el correo electrónico:
info@uygroup.com.uy
------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE:
THE INFORMATION CONTAINED IN THIS E-MAIL IS PRIVILEGED AND CONFIDENTIAL AND IS INTENDED FOR THE EXCLUSIVE USE OF THE ADDRESSEE DESIGNATED ABOVE.
If you are not the addressee, any disclosure, reproduction distribution, or other dissemination or use of this communication is strictly prohibited.
If you have received this electronic mail by error please contact us immediately by telephone: (+598-2) 600-62-00 or by e-mail:
info@uygroup.com.uy
------------------------------------------------------------------------------------------------------------------