Hallo Randall, Am Sonntag, 20. Oktober 2002 um 17:13 schriebst du:
> Andrew, > At 06:58 2002-10-20, Andrew Ellerton wrote: >> >> @="c:\\cygwin\\bin\\bash.exe --login -c \"cd '%1' ; exec /bin/bash >> -rcfile ~/.bashrc\"" >> > >> >can you think of any better way to start bash? >> >the above creates two bash.exe in memory: >> >one executing /etc/profile and the cd-command >> >and one showing the prompt. >> >>The first shell executes a single line of shell commands, namely to change >>directory and run another shell. The second shell runs as the "normal" >>interactive shell. Net effect - looks like the shell has started in a >>different directory. Admittedly a bit hacky, having two shells running for >>no good reason, but it does the job. I'm not sure if shells are very >>expensive in terms of memory. If not, then its a bit kludgey, but >>otherwise its ok. > There are not (ever) two shells running as a result of invoking this > command string. The second one overlays the first in the same process. > That's what the "exec" built-in of the shells does. But I get to see two bash processes with different PID's in the Taskmanager. However, 'ps -e' shows only one... Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
