You are not logged in.
- Topics: Active | Unanswered
Announcement
Download last stable version of GLPI - What can you do for GLPI ? : Contribute
#1 2012-07-26 20:51:34
- mathieu.md
- Member
- Registered: 2012-07-12
- Posts: 20
Monitoring: Command names shouldn't be specific to GLPI?
In order to be really able to work with both flat-files and GLPI configuration at the same time (see my previous bug report), both environments should have their own namespace for check commands.
By example, GLPI plugin Monitoring could prefix all the commands it installs with "glpi_": "check_ping" would become "glpi_check_ping".
This may also be an internal hidden process (ie. command name displayed is "check_ping", but the really registered command is "glpi_check_ping")
Is there any reason against that I'm not aware of?
Offline
#2 2012-07-27 09:54:18
- ddurieux
- Plugins Dev
- From: Propières, France
- Registered: 2005-06-17
- Posts: 7,521
Re: Monitoring: Command names shouldn't be specific to GLPI?
It's possible to name with prefix glpi_
But you can use same commands like your flat commands file no?
Offline
#3 2012-07-27 22:16:57
- mathieu.md
- Member
- Registered: 2012-07-12
- Posts: 20
Re: Monitoring: Command names shouldn't be specific to GLPI?
You cannot use both Monitoring and Shinken flat files commands at the same time, because if there are duplicated names, Shinken will not start.
That's why I though that Monitoring should install commands prefixed by "glpi_" by default.
Offline
#4 2012-07-28 10:16:04
- ddurieux
- Plugins Dev
- From: Propières, France
- Registered: 2005-06-17
- Posts: 7,521
Re: Monitoring: Command names shouldn't be specific to GLPI?
Yes I only use GLPI configuration 
You are a reason to use both ?
Offline