David O'Brien <[EMAIL PROTECTED]> types:
> On Mon, Dec 11, 2000 at 08:14:47AM -0600, Mike Meyer wrote:
> > The problem is that the shared libraries aren't getting found when I
> > run the applix binary after a reboot.
> Why do you say that?  Where is the error message??

I say that because 1) that was VistaSource support's diagnosis, and 2)
doing the ldconfig fixes the problem.  The error message is in last
Sunday, and not currently recreatable.

> > /usr/local/applix/axdata/axshlib are ELF shared objects. I haven't
> > investigated further. If someone got an explanation, I'm all ears.
> Applix sets LD_LIBRARY_PATH in order to find its shared libs.  EXACTLY
> how are you [trying to] run it?

The sequence goes like this: middle click to open a 9menu window. Left
click on the word "applix", which causes 9menu to start a shell
running the command "applix". The shell finds /usr/local/bin/applix on
my path, and runs *that*. At that point, you're running VistaSource's
software, so they should give you the details.

After rebooting last Sunday, I did this - and the disk drives flashed,
and the cpu load went up a bit, and then it all settled back down. I
then followed the instructions I got from VistaSource for shutting
applix down after it fails to start, which is to find and kill all the
processes that have "applix" in the command line and remove the
sockets it creates in /tmp. After that, I su, grep for ldconfig in
/etc/rc, type "ldconfig " at a root prompt, copy and paste the
ldconfig line (which has axshlib in it" to that prompt, and hit
return. Then repeat the process to launch it, only this time I get a
splash screen (why do people want to do that bit of WBD on Unix?) and
the Applixware Office Iconbar before the disk thrashing ends.

And that's all the details I have.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to