PEAR and PECL Command

General discussion on Zend Core for IBM System i
Post Reply
mlavinder
Posts: 87
Joined: Fri Apr 10, 2009 3:12 pm

PEAR and PECL Command

Post by mlavinder » Wed Apr 29, 2009 1:52 pm

I have used the PEAR command to install several PEAR components, but after this latest update to Zend Core 2.6.1, the output (help text and such) created by the PEAR command looks like garbage. I'm not exactly sure why. The output of my own PHP Scripts displays fine. PECL is having the same problem. It doesn't look like PEAR changed in 2.6.1, so I am not exactly sure why the command suddenly isn't working correctly. Any tips would be appreciated.

jeffolen4
Posts: 2
Joined: Fri May 01, 2009 6:57 pm

Re: PEAR and PECL Command

Post by jeffolen4 » Fri May 01, 2009 7:23 pm

I believe that PEAR is included in the Zend Core install and probably is updated when you use the updater. Possibly since you have manually installed some PEAR extensions they got out of synch. Try re-installing the one's you manually installed and see if that fixes the issues.

Jeff

michaelle
Posts: 173
Joined: Sun Dec 21, 2008 1:30 pm
Contact:

Re: PEAR and PECL Command

Post by michaelle » Sun May 03, 2009 3:41 pm

Please check the following post and see if it makes sense for you :

viewtopic.php?f=55&t=495&p=1899&hilit=pear#p1899

User avatar
rodflohr
Zend Global Support
Posts: 56
Joined: Mon Dec 29, 2008 5:28 pm

Re: PEAR and PECL Command

Post by rodflohr » Tue May 05, 2009 2:51 am

Zend R&D is aware of the issue. There is no date set for the fix to be released. In the meantime, they recommend using SSH via a terminal program such as PuTTY:

1. Download Putty client (http://www.chiark.greenend.org.uk/~sgta ... nload.html) [^]
2. Run Putty client in your Windows and enter the i5 ip address marking SSHradio button.
3. Enter i5 user and password
4. cd /usr/local/zend/core/bin
5. pear

This will require that SSH is running on the i5. To run the SSHD daemon on i5/OS:

* The userid that starts the daemon must have *ALLOBJ special authority.
* The userid that starts the daemon must be 8 or fewer characters long.
* Before starting sshd for the first time, you will need to generate host keys:

a. Run the following command in i5/OS to start the PASE shell: CALL QP2TERM
Then, in the PASE shell, run these commands (see the note below if there is a problem):
b. ssh-keygen -t rsa1 -f /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-3.8.1p1/etc/ssh_host_key -N ""
c. ssh-keygen -t dsa -f /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-3.8.1p1/etc/ssh_host_dsa_key -N ""
d. ssh-keygen -t rsa -f /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-3.8.1p1/etc/ssh_host_rsa_key -N ""

You can start the sshd daemon with this CL command:
QSH CMD ('/QOpenSys/usr/sbin/sshd')

Or you can use the command sshd in the PASE shell.

Note: If the commands in step b, c, and d above fail because the directory does not exist, you may need to change the version id of the 'openssh-3.8.1p1' directory. Use this command:

ls /QOpenSys/QIBM/UserData/SC1/OpenSSH/

Use the listed directory name in the path. For example, if the above command shows directory 'openssh-3.5p1', then the command to use for step b is:

ssh-keygen -t rsa1 -f /QOpenSys/QIBM/UserData/SC1/OpenSSH/openssh-3.5p1/etc/ssh_host_key -N ""

Post Reply