site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jan 30, 2008, at 4:59 PM, Martin Costabel wrote: It is definitely /usr/bin/screen that is clobbering PATH. Regards,... -jmpp -- Martin _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/jmpalaciosp%40eml.cc _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Peter Seebach wrote: In message <484969.75807.qm@web83407.mail.sp1.yahoo.com>, David Mackler writes: Hmmm. No screen installed by fink. David, do you perhaps have the Fink "source /sw/bin/init.sh" startup command in your ~/.bashrc script? This non-standard placement would explain that you get the Fink PATH components when you run "screen $SHELL", because then you would get them in any shell, regardless of the environment it runs in. The most common problem I've had with PATH getting clobbered has involved system profile/startup scripts clobbering PATH, and the shell happening to trigger this. Look also at /usr/libexec/path_helper. Thanks for guessing, but none of these explains the behavior I am seeing. The path_helper script would additionally place /usr/local/ bin and /usr/X11/bin on the PATH, which I am not getting. I also put tracers in all the shell startup scripts, and I see that the only ones that are executed are /etc/csh.cshrc and ~/.tcshrc (I have tcsh as login shell). In none of these scripts there is anything influencing PATH. I am setting my PATH in scripts run from / etc/csh.login. I even created a new account with bash as login shell, and I am seeing the exact same behavior; this time it is only ~/.bashrc that is executed. I can't believe I am the only one seeing this. I have seen this on every machine running Leopard I have looked at and on every account I have created or could get my fingers on. I don't have a solution to the problem, but at least a few words of comfort telling you that I'm also experiencing the exact same problem: Tiger's screen, OK; MacPorts' screen, OK; Leopard's screen, no PATH. I have to supply the full path to whatever program I want to run under Leopard's screen, otherwise I get not found errors. Lastly, I've not looked through the problem as extensively as you have, but my setup is rather straight forward with some settings in / etc/profile and some in ~/.profile, pretty standard situation (no path_helper(8) tweaking anything). I don't see what could be hampering screen's environment in my shell configuration, so I'm also guessing it must be a problem with screen itself. This email sent to jmpalaciosp@eml.cc This email sent to site_archiver@lists.apple.com