Could someoje tell me how to compile PHP, which is already installed, with the ./confgure --with-interbase=opt/interbase? OR how I can get the system (SuSE 8.1) to recognize the 4.3 PHP that I installed? Any hints wouild be helpful. Art
Hi Art, Art Fore wrote:
Could someoje tell me how to compile PHP, which is already installed, with the ./confgure --with-interbase=opt/interbase? OR how I can get the system (SuSE 8.1) to recognize the 4.3 PHP that I installed?
Have you already programmed a test-page (e.g.. 'test.php') to see what version you are using - and which configuration is available? It should be saved somewhere in your 'htdocs'-Directory (root-Directory of your apache) and look like this: <html> <body> <?php phpinfo (); ?> </body> </html> When you enter the location of this page in a browser, it should give you a lot of information. I hope, this might help you a little. Dirk
That is the problem, test page shows 4.2.2 but I installed 4.3 with interbase support. Art On Sat, 2003-02-15 at 04:54, dirk schlangen wrote:
Hi Art,
Art Fore wrote:
Could someoje tell me how to compile PHP, which is already installed, with the ./confgure --with-interbase=opt/interbase? OR how I can get the system (SuSE 8.1) to recognize the 4.3 PHP that I installed?
Have you already programmed a test-page (e.g.. 'test.php') to see what version you are using - and which configuration is available?
It should be saved somewhere in your 'htdocs'-Directory (root-Directory of your apache) and look like this:
<html> <body> <?php phpinfo (); ?> </body> </html>
When you enter the location of this page in a browser, it should give you a lot of information.
I hope, this might help you a little.
Dirk
Hi once more, Art Fore wrote:
That is the problem, test page shows 4.2.2 but I installed 4.3 with interbase support.
Ok - then your php-support is generally working - and you're looking for a way to make the 4.3 version available, right? Can you tell me (us) where you downloaded the php-4.3-package? Perhaps the 'standard-compilation' doesn't install php in the '/usr/share/php' directory (where I have my php-Documents installed with SuSE 8.1), but elsewhere? Maybe you could search for certain documents (e.g. 'System.php') and see if they appear twice in your system(in this case outside of '/usr/share/php/ ...'). Then, you could perhaps - this is only an idea, because I haven't tested it - set the paths and directories in the '/etc/php.ini'-Configuration-File. I hope, this might help you a little? Dirk
Got the 4.3 from the php.org site. Will check your suggestions Tuesday when I go back to work. Thanks for the info. Art On Sat, 2003-02-15 at 09:34, dirk schlangen wrote:
Hi once more,
Art Fore wrote:
That is the problem, test page shows 4.2.2 but I installed 4.3 with interbase support.
Ok - then your php-support is generally working - and you're looking for a way to make the 4.3 version available, right?
Can you tell me (us) where you downloaded the php-4.3-package?
Perhaps the 'standard-compilation' doesn't install php in the '/usr/share/php' directory (where I have my php-Documents installed with SuSE 8.1), but elsewhere?
Maybe you could search for certain documents (e.g. 'System.php') and see if they appear twice in your system(in this case outside of '/usr/share/php/ ...').
Then, you could perhaps - this is only an idea, because I haven't tested it - set the paths and directories in the '/etc/php.ini'-Configuration-File.
I hope, this might help you a little?
Dirk
After a lot of confusion on my part I got Samba running in Suse Pro. 8.1 My question now is why do I have to go to Swat and start SMBD and NMBD everytime I boot up? Isn't there some way for me to make these start on bootup? I looked in inetd and didn't see the items there. Thanks, Roy
Go into Yast2, under the System category and select "Edit Run Level"... or from the command line as root, do a "chkconfig -l" to find what you want to change, then a "chkconfig -s <service> on" - herman Roy D Mercer wrote:
After a lot of confusion on my part I got Samba running in Suse Pro. 8.1 My question now is why do I have to go to Swat and start SMBD and NMBD everytime I boot up? Isn't there some way for me to make these start on bootup? I looked in inetd and didn't see the items there.
Thanks, Roy
On Saturday 15 February 2003 22:40, Roy D Mercer wrote:
After a lot of confusion on my part I got Samba running in Suse Pro. 8.1 My question now is why do I have to go to Swat and start SMBD and NMBD everytime I boot up?
Probably because it would quite a huge security risk to have smbd and nmbd run automatically.
Isn't there some way for me to make these start on bootup?
No doubtedly. You can use either YaST2 or chkconfig: 1. YaST2: System->Runlevel Editor. From there you can put checkboxes next to the runlevels you want it to start on. Good choices are 3 and 5. 2. chkconfig: # chkconfig -l smb nmb smb 0:off 1:off 2:off 3:off 4:off 5:off 6:off nmb 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig nmb 35 # chkconfig smb 35 # chkconfig -l smb nmb smb 0:off 1:off 2:off 3:on 4:off 5:on 6:off nmb 0:off 1:off 2:off 3:on 4:off 5:on 6:off # If you use an xterm, it's nice and color-coded...
I looked in inetd and didn't see the items there.
Samba does not use inetd or any inet daemon.
On Saturday 15 February 2003 9:50 pm, Herman Knief wrote:
Go into Yast2, under the System category and select "Edit Run Level"... or from the command line as root, do a "chkconfig -l" to find what you want to change, then a "chkconfig -s <service> on"
- herman
Thank you much. I knew it was somewhere but for the life of me couldn't find it. Roy
On Sat, 2003-02-15 at 21:55, Karol Pietrzak wrote:
On Saturday 15 February 2003 22:40, Roy D Mercer wrote:
After a lot of confusion on my part I got Samba running in Suse Pro. 8.1 My question now is why do I have to go to Swat and start SMBD and NMBD everytime I boot up?
Probably because it would quite a huge security risk to have smbd and nmbd run automatically.
Actually, It's not a security risk if you're using a good firewall and you're binding samba to your internal IP only (bind interfaces only = yes & interfaces = 192.168.0.5/24) The real issue, is the firewall. If you don't let anything into ports 137-139, you'll never have a problem! :) -- Travis
participants (6)
-
Art Fore -
dirk schlangen -
Herman Knief -
Karol Pietrzak -
Roy D Mercer -
Travis Owens