Difference between revisions of "Talk:OCS Inventory Tools"
| Line 60: | Line 60: | ||
---- | ---- | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==dependencies== | ==dependencies== | ||
Revision as of 14:18, 10 November 2007
known bugs
There are still some bugs in this RPM... Help us to fix them!
ipdiscover bug
ipdiscover and SME
We need to make ipdiscover working on SME.
no we don't, we've wasted enough time on this, just say to use a client (If they want to force discover)
ipdiscover-util.pl
This script used by the web interface do not seem to work too.
First thing to do is to change the password in this file...
... my $dbhost = 'localhost'; my $dbuser = 'ocs'; my $dbpwd = 'ocs'; my $db = 'ocsweb'; my $dbp = '3306';
The password should be dynamical as this is a perl script. We need to use esmith::ConfigDB or something else to retrieve this value... I was unable to handle that.
Also a problem, the script cannot be executed. I try to add script handler for .pl but it didn't worked...
www/ocs/install.php bugs
New doc, enjoy!
=> Why do we need really an admin account? Why can't we use ocs?
If you encounter any problem with files insertion, try setting the global max_allowed_packet mysql value to at least 2M in your server config file.
How to set this value for ocs only?
=> install.php is needed, as you now know. But the file can be renamed or secured when not needed ;-)
I didn't use this screenshot finally... It shows default MaxUpload can be seen here & ocsagent.exe not present
File:OCS-installphp-warning.png
Should we delete it?
future RPM
What will be fixed in next RPM release...
MaxUpload
Default value will raise to 100M (OpenOffice ready)
secure install.php
What is the best way to secure this file?
Move it? Rename it? chmod 400?
If this file is secured, we need to document that in the article.
sg
If we abandon the MySQL importation method we can delete it
Admins will have USB keys, they have space for the C:\ocs-ng\ files and can use the manual method
this also simplifies the wiki a lot and negates the need to split it up
sn
dependencies
just supply the .tar.gz
add all the dependacies in smeserver-inventory-tools to make sure the user has installed them
wiki page
split page
I'd like to move somethings to a sub page and just show the most likely options
4.2.2 ocsagent.exe
4.2.3 OcsLogon.exe
in time, 3.3.1 Old RPMs version
5.2.1 Modifying default behaviour
there must be a lot of ways this could be used, why make everyone think of them themselves when it could be spelled out
this could be a new page, Application deployment
this could include other ways to deploy, eg using netlogon.bat
others can work on this cool34000 has done enough
glpi
someone who uses this may like to add some more information on how to use it, some link to more docs at least
