Re: Applix problems (Was: /usr/local abuse)
On Mon, Dec 11, 2000 at 05:45:07PM -0600, Mike Meyer wrote: Others have noted that the script it installs in $(PREFIX)/bin/applix has /usr/local wired into it, though. Yes, I will bring that up tomarrow with the BSDi developer putting together the next revision of it. Maybe I should have mentioned I work for BSDi and thus can possibly make suggestions to over come issues. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Applix problems (Was: /usr/local abuse)
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?? /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? -- -- David ([EMAIL PROTECTED]) P.S. details are good.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Applix problems (Was: /usr/local abuse)
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. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Applix problems (Was: /usr/local abuse)
On Mon, Dec 11, 2000 at 05:24:19PM -0600, Mike Meyer wrote: At that point, you're running VistaSource's software, so they should give you the details. Then I'll just back out of trying to help figure out why many others can run it outside of /usr/local. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Applix problems (Was: /usr/local abuse)
David O'Brien [EMAIL PROTECTED] types: On Mon, Dec 11, 2000 at 05:24:19PM -0600, Mike Meyer wrote: At that point, you're running VistaSource's software, so they should give you the details. Then I'll just back out of trying to help figure out why many others can run it outside of /usr/local. While I appreciate the help, it seems you missed a point. I reinstalled it in /usr/local - and ran into the exact same problem I had with it outside /usr/local (that it requires some frobbing after a reboot to work properly). I was wrong when I said it didn't like being moved; it just took rebooting to expose the problem, and it wasn't until last Sunday that I rebooted with it installed in /usr/local. Others have noted that the script it installs in $(PREFIX)/bin/applix has /usr/local wired into it, though. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Applix problems (Was: /usr/local abuse)
David O'Brien [EMAIL PROTECTED] types: On Sun, Dec 10, 2000 at 11:42:37PM -0600, Mike Meyer wrote: On the other hand, Applixware Office ships a precompiled package for /usr/local, and doesn't like being installed anywhere else. Which means I've got a couple of hundred megabytes being backup up for no good reason :-(. Mine lives in /usr/opt just fine. What signs do you have of it not liking being out of /usr/local ? Tony Maher [EMAIL PROTECTED] types: On the other hand, Applixware Office ships a precompiled package for /usr/local, and doesn't like being installed anywhere else. Which means I've got a couple of hundred megabytes being backup up for no good reason :-(. Really?! I have it installed in /opt/applix and I dont think there are any symlinks anywhere in /usr/local for it. It works fine. My bad. I discovered last night that the problems I though were associated with it not being installed in /usr/local are occuring even though I *did* install it in /usr/local. Of course, last night was the first time I've rebooted with it installed in /usr/local, and that's when the problem shows up. The problem is that the shared libraries aren't getting found when I run the applix binary after a reboot. Here's the relevant part of /etc/rc.conf: ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/opt/lib /usr/opt/pgsql/lib /usr/opt/pilot/lib /usr/local/lib /usr/local/applix/axdata/axshlib" ldconfig_paths_aout="" # No aout in my userlands After the first reboot, running applix just causes off a lot of disk activity and creates processes and a socket in /tmp. Killing them, removing the file in /tmp, and then running "ldconfig $ldconfig_paths" (though I do it with cut-n-paste) solves the problem, and I can run applix just fine. Failing to do the ldconfig (at least, with applix somewhere other than /usr/local) doesn't solve the problem. As far as I can tell, the only difference is that /etc/rc runs the ldconfig as "ldconfig -elf". All the files in /usr/local/applix/axdata/axshlib are ELF shared objects. I haven't investigated further. If someone got an explanation, I'm all ears. Thanx, mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
