Hanspeter,
Thanks! That was it. And this one was completely my fault. I created a .tcshrc file late last night and while it still had the "source /sw/bin/init.csh" line in it, it seemed to conflict anyways.
On Apr 15, 2004, at 5:13 PM, Hanspeter Niederstrasser wrote:
On Thu, 15 Apr 2004 [EMAIL PROTECTED] wrote:
i logged into my server today and could not launch any binaries installed into /sw/bin. I checked my .cshrc file and as it should the line
source /sw/bin/init.csh was there as it should be.
but I could still not run any binaries unless i typed out the full path
"/sw/bin/binary"
I have never encountered this problem before and so I logged in as a
different user and everything worked as it should. has anyone seen this
behavior before?
Check that there isn't a .tcshrc file in the home dir for the non-working
user. If tcsh detects .tcshrc, it reads that and ignores .cshrc. If some
program installed a .tcshrc file, add the "source /sw/bin/init.csh" line
to .tcshrc and all should be well.
Hanspeter
You can still use the .tcshrc file, just add the line "source ~/.cshrc" to it. You might also want to source /usr/share/tcsh/examples/rc.
James
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
