On Wednesday 24 December 2008 00:29, Denys Vlasenko wrote: > On Tuesday 23 December 2008 20:09, Robert P. J. Day wrote: > > On Tue, 23 Dec 2008, Vladimir Dronnikov wrote: > > > > > Again, telnetd spawn /bin/login or whatever you specify with -l > > > option; thus telnetd has nothing to do with $PATH on its own. > > > > > > Have you checked your login helper, Robert? > > > > i verified that telnetd is being invoked initially with > > > > /usr/sbin/telnetd -l /bin/sh > > > > where /bin/sh -> busybox. so since the entire login process is being > > bypassed entirely, what are my options to modifying sh's search path? > > thanks. > > Unlike bash, ash does not have anything like ~/.bashrc, > which could be useful here. ash run as shown above > would not run any startup script. You need to run it either > with -l or as -/bin/sh (su, login, sulogin do that). > > Or you can cook up a patch to support ~/.ash
Or you can set PATH *prior to running telnetd*. telnetd passes environment to children unmodified. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
