[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bash job control goes haywire under Solaris 2.6 / LDAP

From: bash-user
Subject: Bash job control goes haywire under Solaris 2.6 / LDAP
Date: Mon, 30 Apr 2001 21:23:22 -0400 (EDT)

Configuration Information [Automatically generated, do not change]:
Machine: sparc
OS: solaris2.6
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc' 
-DCONF_OSTYPE='solaris2.6' -DCONF_MACHTYPE='sparc-sun-solaris2.6' 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -I.  -I. -I./include -I./lib 
-I//include -g -O2
uname output: SunOS minipeace 5.6 Generic_105181-26 sun4u sparc 
Machine Type: sparc-sun-solaris2.6

Bash Version: 2.05
Patch Level: 0
Release Status: release


Under the version of bash stated above, we have a problem with job
control.  One note about the machine that we're running bash-2.05 on:
it's a SPARC running Solaris 2.6 with a current set of (Solaris)
patches and it's also running the nss_ldap-150 package from padl.com to
perform lookups/authentication for user information.

Local users do not experience the problem listed below.  Only users
(whose credentials, etc) who are handled by LDAP experience these
problems.  Now, I'd write this off as a bash/LDAP interaction problem,
but we're also using the same configuration under Solaris 7 and
GNU/Linux and there are no problems.

Basically, a user can login to the machine and /bin/bash gets executed,
BUT any command that the user runs is automatically suspended.  The
command can get executed if we 'fg' it, but this is a tremendous
nuisance and not desirable behavior.  Bash internals (variable
assignment, echo, etc), on the other hand, work just fine.

I've been able to "make this problem go away" by disabling job control
with configure and reinstalling the shell.  I'm then able to both
execute commands and use bash internals.  But of course this isn't what
we want to do either.


1. login to machine

login: xxxx
Password: xxxxxxxx

2. /bin/bash gets executed and I see prompt


3. I am able to assign a variable:

bash-2.05$ trash='here here!'

4. I am able to use echo:

bash-2.05$ echo $trash
here here!

5. But I can't run commands, as they are immediately suspended:

bash-2.05$ ls

[1]+  Stopped                 ls

6. I can only run commands if I 'fg' the suspended process:

bash-2.05$ fg
[output of ls]


The only "fix" is to disable job control and this truly doesn't fix the
problem, since what's a Unix shell without job control?  ;-)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]