On Mon, 2003-10-20 at 11:32, Stuart Jansen wrote: > I have never heard of .kshrc, are you sure such a beast exists?
It does if you set ENV=.kshrc in your .profile then it better exist :) > The crux of your problem was the sentence "This server management tool > ssh-es to the HP-UX machine." SSH/KSH detect that there is no tty > attached to the session, so it doesn't bother running the .profile. I > have found no way to force KSH to source the .profile. This causes an > annoying umask bug for me. Well, yes, that does explain it. > Are the scripts generic enough that they would work in bash? Switching > the users shell to bash and putting the ulimit in the .bashrc should > do the trick. I was just testing out a wrapper script that I would have theses auto-generated start scripts call, instead of the actual binary they want to call. Then the wrapper could set the ulimit and then call the actuall binary. Just switching to bash might be less kludgey though... > If this is proprietary software, I should think there would be a > support license attached. Make them solve it. HAHAHAHAHAHA. Oh sorry. That was a good one. Actually we worked long and hard with them and they could not tell us why the server was not running. Finally we put the exact error message into google and found a number of pages explaining that people had been seeing this problem under solaris and the ulimit fixed it. We quickly discovered it fixed our problem too. It makes no sense to anyone, but it magically works. I suppose if we could get past the college student who's doing the tech support and talk to some developers, or could just look at the source code, we might have a chance of getting some answers... Anyway, thanks for explaining the ksh/ssh not sourcing the .profile thing. I'll definately hold on to that tidbit of info! Bryan ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
