topic Re: Bus error during su - in Operating System - HP-UX

Bus error during su -

Radek.B — Tue, 27 Mar 2007 09:23:13 GMT

Hi,
I've problem with su - under informix user.
Using "ksh" (etc/passwd) error message is "Memory fault" and using "sh" I can see "Logout Bus error". User profile is ok.
Any ideas ? Thx a lot

Re: Bus error during su -

A. Clay Stephenson — Tue, 27 Mar 2007 09:36:16 GMT

This has to be a problem either in user informix's .profile or in a script or program called (or sourced) from within .profile. This is very easy to test.
Do a "su informix" (without the "-") . If that works the user's .profile is the problem and you should then be able to take normal debugging steps. I almost never use the "-" version of su because I typically want to do things under cron or rc. There are usually sections of .profiles that expect the session to be interactive and will hang or cause unexpected results when stdin is not a terminal. My preferred method is to set up a separate file (e.g. /usr/local/bin/informix_env.sh) that is sourced by both my cron'ed script and the user's .profile.

Re: Bus error during su -

Radek.B — Tue, 27 Mar 2007 09:53:27 GMT

su informix works. But although I replaced .profile with empty one, it was the same.

Re: Bus error during su -

A. Clay Stephenson — Tue, 27 Mar 2007 10:01:18 GMT

Okay, are there any special conditions that apply to user informix in /etc/profile? You also need to look at .kshrc (if it exists).

Re: Bus error during su -

Radek.B — Tue, 27 Mar 2007 10:23:42 GMT

yes there is but only basic, I'll probably need to debug whole file :(

Re: Bus error during su -

A. Clay Stephenson — Tue, 27 Mar 2007 10:54:34 GMT

In your case, I would replace your /etc/profile with an original version. It's normally a bad idea to put any special conditions in /etc/profile. The only branching conditions in /etc/profile should be for user root and then anyone else. Informix's special conditions should be in his .profile or as I mentioned earlier in a file like "/usr/local/bin/informix_env.sh" that both .profile and any cron'ed script source using the shell's . (dot) operator. There should be no exits or returns in the sourced file.

Re: Bus error during su -

Bill Hassell — Tue, 27 Mar 2007 14:12:35 GMT

As mentioned, your profiles need debugging. The only practical way to do this is to trace every step using set -x. Add the line:

set -x

at the start of /etc/profile and you will see somewhere along the way that a command or program has crashed during the processing of all the profile statements. The set -x option will be carried into all sourced settings files.

Re: Bus error during su -

Radek.B — Thu, 29 Mar 2007 03:27:41 GMT

Thanks all for a help, but looks like that problem is somewhere else (debug is ok). I have founded that nbuf was on 100% (fixed vaue), now it is dymanic but no help.