Maybe you can enlighten me. As far as I can tell APOC is a client/server method for setting/getting configuration parameters. I keep getting errors like:
[ApocSource] Source apoc:readonly: is unavailable: Failed: [ApocPapi] Cannot initialise PAPI: PAPI Connection Failure. Based on your experiences, how do I resolve this error? Do I need to set up an LDAP service with APOC to start PAPI? How about laptop users? Is this really necessary? Thanks, Gary > APOC was initially an irritant, that couldn't be had, > or obtained when building JDS...but could be bypassed > with the correct option IIRC "--without-apoc" or > something like that...but no...I remained irritated > that it wasn't there. > > Then I learned to read....Found that "JDS > Configuration Manager" a.k.a "Sun Desktop Manager" > was available, downloaded it and installed....and > realized that svc:/network/apocd/udp:default was > disabled in SXDE 09/07...and probably elsewhere. > > I remained mystified over APOC, GConf and > Schemas....then I learned to read bigger > words....which wasn't really necessary...because the > Desktop Manager Wizard was more than happy to help me > along with mapping, profiles and all the other things > I had glossed over in the documentation. > > Maybe someone will find the Sun Desktop Manager 09/07 > release as educational as I did...and I take back all > those *expletive deleted* thoughts I had because APOC > was missing in action for the JDS build....;) This message posted from opensolaris.org
