On Sunday 27 March 2011 20:42, Seb wrote: > Le Sun, 27 Mar 2011 19:03:16 +0100 > Denys Vlasenko <[email protected]> a écrit: > > > > > Apparently, your /bin/su is a symlink to busybox which doesn't have > > > > su applet enabled. > > > > > > Impossible, as I install busybox directly as /bin/ash (no symlink), > > > > Your /bin/su, NOT your /bin/ash, is bad. > > What "ls -l `which su`" says? > > $ ls -l `which su` > -rws--x--x 1 root root 56229 2010-02-28 21:16 /bin/su > > > > the su is the one of my Slackware (shadow-4.1.4.2). Are you sure here > > > the user uses the ./ash exec as login shell? Below is the test I do: > > > > > > # useradd unibug -s /bin/ash -d /tmp -p "" > > > # su - unibug > > > su: applet not found > > > > Look closely above WHAT EXACTLY fails. It's su command. I bet even > > "su --help" will fail. > > $ su --help > Usage: su [options] [LOGIN] > > Options: > -c, --command COMMAND pass COMMAND to the invoked shell > -h, --help display this help message and exit > -, -l, --login make the shell a login shell > -m, -p, > --preserve-environment do not reset environment variables, > and keep the same shell > -s, --shell SHELL use SHELL instead of the default in > passwd
Hmm. Can you run "strace -s99 -oLOG su - unibug" and post resulting LOG file? -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
