[ Index ] |
|
Code source de eGroupWare 1.2.106-2 |
1 2 phpSysInfo 2.5.2-rc1 - http://phpsysinfo.sourceforge.net/ 3 4 Copyright (c), 1999-2002, Uriah Welcome (precision@users.sf.net) 5 Copyright (c), 1999-2001, Matthew Snelham (infinite@users.sf.net) 6 7 8 CURRENT TESTED PLATFORMS 9 ------------------------ 10 - Linux 2.2+ 11 - FreeBSD 4.x 12 - OpenBSD 2.8+ 13 - NetBSD 14 - Darwin/OSX 15 - WinNT 16 - PHP 4.x and 5.x 17 18 If your platform is not here try checking out the mailing list archives or 19 the message boards on SourceForge. 20 21 22 INSTALLATION AND CONFIGURATION 23 ------------------------------ 24 Just decompress and untar the source (which you should have done by now, 25 if you're reading this...), into your webserver's document root. 26 27 There is a configuration file called config.php.new. If this a brand 28 new installation, you should copy this file to config.php and edit it. 29 30 - make sure your 'php.ini' file's include_path entry contains "." 31 - make sure your 'php.ini' has safe_mode set to 'off'. 32 33 Please keep in the mind that because phpSysInfo requires access to many 34 files in /proc and other system binary you **MUST DISABLE** php's 35 safe_mode. Please see the PHP documentation for information on how you 36 can do this. 37 38 If you use the apc pecl extension with apc.optimization="1" then phpSysInfo might 39 break in the XPath.class. Turn this option off, and it will work with apc. 40 41 That's it. Restart your webserver (if you changed php.ini), and viola! 42 43 44 KNOWN PROBLEMS 45 -------------- 46 - phpSysInfo is not full compatible with SELinux Systems 47 - small bug under FreeBSD with memory reporting 48 - XML will not work properly/validate under anything except Linux and 49 Net/FreeBSD The "This is Under Development" warning gets printed and 50 isn't valid in XML. 51 52 53 PLATFORM SPECIFIC ISSUES 54 ------------------------ 55 - FreeBSD 56 There is currently a bug in FreeBSD that if you boot your system up and 57 drop to single user mode and then again back to multiuser the system 58 removes /var/run/dmesg.boot. This will cause phpsysinfo to fail. A bug 59 has already been reported to the FreeBSD team. (PS, this may exist in 60 other *BSDs also) 61 - Windows with IIS 62 On Windows systems we get our informations through the WMI interface. If you 63 run phpsysinfo with the IIS webserver, phpsysinfo can't connect to the WMI 64 interface for security reasons. At this point you MUST set an authentication 65 mechanism for the directory in the IIS admin interface. Then you will be asked 66 for an user and a password when opening the page. At this point it is necassary 67 to log in with an user that will be able to connect to the WMI interface. 68 If you use the wrong user and/or password you might get an "ACCESS DENIED ERROR". 69 70 WHAT TO DO IF IT DOESN'T WORK 71 ----------------------------- 72 First make sure you've read this file completely, especially the 73 "INSTALLATION AND CONFIGURATION" section. If it still doesn't work then 74 you can: 75 76 Submit a bug on SourceForge. (preferred) 77 (http://sourceforge.net/projects/phpsysinfo/) 78 79 80 OTHER NOTES 81 ----------- 82 If you have an great ideas or wanna help out, just drop by the project 83 page at SourceForge (http://sourceforge.net/projects/phpsysinfo/) 84 85 The "Unauthorized reading files on phpSysInfo" reported by 86 Albert Puigsech Galicia <ripe@7a69ezine.org> and Wolter Kamphuis 87 <security@wkamphuis.student.utwente.nl> is fixed in version 2.2. 88 http://www.securityfocus.com/archive/1/319713 89 90 91 LICENSING 92 --------- 93 This program and all associated files are released under the GNU Public 94 License, see COPYING for details. 95 96 97 $Id: README 21228 2006-04-06 13:52:08Z ralfbecker $
titre
Description
Corps
titre
Description
Corps
titre
Description
Corps
titre
Corps
Généré le : Sun Feb 25 17:20:01 2007 | par Balluche grâce à PHPXref 0.7 |