On Sunday 27 March 2011 19:44, Seb wrote: > Le Sun, 27 Mar 2011 17:26:46 +0100 > Denys Vlasenko <[email protected]> a écrit: > > > > > Please post your .config > > > > > > Sorry, this is the same as the one I've posted first. I > > > nevertheless attach the last one I've tested with, just to be sure. > > > > Can't reproduce with your .config: > > > > # ./ash > > /tmp # su - > > ... > > hostname:~# exit > > logout > > /tmp # > > > > > > 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? > 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. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
