ID: 39318 Updated by: [EMAIL PROTECTED] Reported By: RQuadling at GMail dot com -Status: Open +Status: Assigned Bug Type: Documentation problem Operating System: Windows XP SP2 PHP Version: Irrelevant -Assigned To: +Assigned To: rquadling New Comment:
I still think this is bogus, but feel free to take care of it yourself :) Previous Comments: ------------------------------------------------------------------------ [2006-10-31 12:21:54] RQuadling at GMail dot com You don't HAVE to use a non LocalSystem account. BUT, if you do not, you will not have access to elements outside of the box. It is relevant to PHP because the account you use to run Sambar Server as a service is the same account that is used by PHP when you attempt to access network resources. It is probably no different to saying that if you are using IIS, then you need to create permissions on network resources for the IUSR account. The issue is that the server will happily run when you use local resources and LocalSystem account. I suppose this would apply to ALL webservers. The account being used to run the webserver has to have permissions granted to it to access remote resources. Maybe an documentation entity detailing this could be added to all the webserver setup pages for Windows rather than just Sambar. If you are not accessing remote resources, then there is no need to change the account. ------------------------------------------------------------------------ [2006-10-31 12:12:29] [EMAIL PROTECTED] So in order to use Sambar+PHP you have to configure Sambar to use "non localsystem account"? I'm sorry. I just don't see how this is relevant. Explain to me again why this should be documented in the PHP manual rather then Sambar (having in mind that the PHP docs will never cover every (any?) 3rd party software out there)? ------------------------------------------------------------------------ [2006-10-31 11:32:53] RQuadling at GMail dot com Because, the default account used by installing Sambar Server as a service has no impact upon the normal use or operation of Sambar Server. When you add PHP to Sambar, the default account is fine for all locally stored files. You are not getting anything other than local files. But accessing the remote files is being performed by PHP and NOT Sambar Server. Sambar in effect "launches" PHP and therefore this is a PHP issue affecting the Sambar Server Service. ------------------------------------------------------------------------ [2006-10-31 11:27:48] [EMAIL PROTECTED] And why do you think this is a PHP documentation issue? ------------------------------------------------------------------------ [2006-10-31 11:00:43] RQuadling at GMail dot com Description: ------------ What started as a quick upgrade to a script which works via CLI mode to be also accessible via a web interface has taken me WAY too long (about 2 days). So, I'm officially dim today. Anyway. If you are using Sambar Server as a service (C:\Program Files\Sambar Server\bin\ntserver -i) AND you want your scripts to access files which are NOT held locally (using a \\SERVER\SHARE\DIRECTORY\FILE mechanism), then you need to use a NON LocalSystem account. You can configure the account to a particular named user via the Services applet in the Control Panel. You will need to supply a password for the account. If you do not do this, you will not be able to use PHP commands like fopen, file_exists, etc to access remote files. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=39318&edit=1
