× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WEB400
  3. December 2017

Re: ToolkitAPI shows as SYMLNK

Is there any particular reason you don't want it to be a symlnk? The
zend install created the symlnk as well as the directory linked too.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Don
Brown
Sent: Wednesday, December 20, 2017 3:10 PM
To: Web400@Midrange. Web400
Subject: [WEB400] ToolkitAPI shows as SYMLNK

I am setting up php on a 7.3 box for the first time.

I have installed Zendsvr7 and that completed normally.

I have installed xmlservice 1.9.9.3

When i look in /usr/local/zendphp7/share/

I expected to see a directory ToolKitAPI but it shows as a SYMLNK

The same for ZendFramework and ZendFramework2

Why is this so ?

Should I just delete these and copy from the directories from another
system ?

Are these directories created as part of the Zend server install ?

Thank you in advance for any assistance



Don Brown


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list
To post a message email: WEB400@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.