On Fri, Mar 18, 2005 at 06:48:02PM +0100, Nicolas François wrote: > On Fri, Mar 18, 2005 at 11:13:03AM +0100, Javier Fernández-Sanguino Peña > wrote: > > On Fri, Mar 18, 2005 at 12:00:25AM +0100, Nicolas François wrote: > > > Hi, > > > > > > On Thu, Mar 03, 2005 at 02:23:04PM +0100, Christoph Martin wrote: > > > > >/usr/lib/tiger/systems/Linux/2/check_passwdspec: [: too many arguments > > > > >/usr/lib/tiger/systems/Linux/2/check_passwdspec: [: too many arguments > > > > >/usr/lib/tiger/systems/Linux/2/check_passwdspec: [: too many arguments > > > > >/usr/lib/tiger/systems/Linux/2/check_passwdspec: [: too many arguments > > > > > > They are caused by a password set to ! (this is the case for postfix) in > > > systems/Linux/2/check_passwdspec, line 87 > > > [ "$Tiger_Check_PASSWD_SHADOW" = 'Y' -a -s /etc/passwd -a "$pwd" != "x" ] > > > > Maybe that's because the construct is bash specific. Does > > > > [ "$Tiger_Check_PASSWD_SHADOW" = 'Y' ] && [ -s /etc/passwd ] && [ "$pwd" > > != "x" ] > > > > Work for you? > > Yes, it does.
Since then, I tested with other shells: It doesn't work with ash 0.3.8-37 or 0.5.2-2: [: 91: x: unexpected operator but the reversed test ([ "x" != "$pwd" ] instead of [ "$pwd" != "x" ]) works. This is very empirical. I could not find anything regarding this on the ash/bash man pages. -- Nekral
