Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

stoid

macrumors 601
Original poster
I'm using the terminal version of Folding@home, and know every time I open a new terminal window it launches the OSX-3.25 and starts the folding process without giving me an option for input. Help me get my terminal back!!
 
post ur .login file in ur home dir

do a cat .login to show it
 
From the Terminal app, I did File>New Command... and typed "cat .login" and got:

HUS412A:~ briankersten$ cat .login; exit
alias start 'cd ~/F@H1; ./OSX-3.25 -local -advmethods > /dev/null &'

alias stop 'killall OSX-3.25'

alias work '~/.work'

alias rid '~/.rid'

alias pause 'killall -STOP -m "FahCore*"'
alias resume 'killall -CONT -m "FahCore*"'
logout
[Process completed]

does that help?
I'm not terminal savvy, but I do use it occasionally.
 
Re: Folding Hijacked my Terminal!

Originally posted by stoid
I'm using the terminal version of Folding@home, and know every time I open a new terminal window it launches the OSX-3.25 and starts the folding process without giving me an option for input. Help me get my terminal back!!

In your terminal preferences there is an option to execute a command when creating a new terminal window. Is this set?
 
Originally posted by mc68k
post ur .login file in ur home dir

do a cat .login to show it

Question unrelated to this thread:

I don't use the scripts, but I noticed that stop is aliased to something folding related. stop is a csh/tcsh job control built-in, is this a potential conflict?

Regards
 
Re: Re: Folding Hijacked my Terminal!

Originally posted by vannote
In your terminal preferences there is an option to execute a command when creating a new terminal window. Is this set?

Is this what you mean?

I fiddled with this but it didn't change anything, I'm clueless here, thanks.
 

Attachments

  • picture 2.jpg
    picture 2.jpg
    59 KB · Views: 322
Re: Re: Re: Folding Hijacked my Terminal!

Originally posted by stoid
Is this what you mean?

I fiddled with this but it didn't change anything, I'm clueless here, thanks.

Ok, your clean, I just wanted to rule out the obvious. Now, is there anything in your .bashrc that would fire off folding?

Go to your home directory at do a cat .bashrc

Again, I don't now much about the scripts floating around to control the CLI folding client. I just use the CLI client as is. mc68k is probably the one to troubleshoot this.
 
Re: Re: Re: Re: Folding Hijacked my Terminal!

Originally posted by vannote
Ok, your clean, I just wanted to rule out the obvious. Now, is there anything in your .bashrc that would fire off folding?

Go to your home directory at do a cat .bashrc



How, I am rather confused... I can't type it in a new terminal window, because every terminal window I open starts the folding script. If I move the folding script is gives me an error, and then [process completed]. If I do a "New Command" from the file menu with a cat .bashrc it says something like command not found and then [process completed].
 
ok i'm confused too. try getting rid of folding using the rid command.

quit out of the terminal, then fire up the terminal again to see if the problem persists.

try reinstalling afterwards...i have never ur situation happen, but panther does throw in some more variables i guess. maybe a bad script install?

the main files for controlling folding are the crontab and the .login file. the .login file u posted is the same thing. crontab doesn't have anything to do with ur problem.

tell me how it goes...i hate to have u lose work, but sometimes those r the breaks
 
Originally posted by stoid
I didn't use your scripts mc68k, I've just got the regular OS X-3.25 file running in the terminal.

Yes, I can even restart my machine, and the problem will still persist.
the .login file u posted was from my scripts

looks like ur in bash shell too

try changing ur default shell in Netinfo

users>briankersten>shell

change it to /bin/tcsh
 
I changed it to /bin/tsch as you mentioned, both within the Terminal preferences (the screenshot I posted earlier, and within the NetInfo application. I think that I may have install the scripts, then changed my mind, and decided to use the regular console version from the folding@home website.

I tried the rid command and it gave me this:

[HUS412A:~] brianker% rid; exit
tcsh: rid: Command not found.
logout
[Process completed]



edit: I tried re-downloading/re-installing the script, but it gave the same information.
 
edit your .login file, change 'start' and 'stop' to something else (like 'start_fold' / 'stop_fold') and see if that does anything.

you can edit your .login w/ TextEdit. browse to Home and type '.login' in the 'Go To' area.

if that solves your problem, then somewhere 'start' is being called. maybe in .bashrc or something, or maybe it's built into the Panther shell startup routine.
 
Originally posted by stoid
Not so much

Here's the response from "the man behind the curtain"

[HUS412A:~] brianker% rm .login; exit
rm: .login: No such file or directory
logout
[Process completed]

Also, you may want to change your Terminal preferences to the "Execute the default login shell using /usr/bin/login" selection. This is the initial setting.
 
Okay, I changed my Terminal preferences to the "Execute the default login shell using /usr/bin/login" selection, but I don't know how to access the .login file as mentioned by zimv20. Is this through the Finder? Where is the goto bar? I am in Panther if that makes difference.

And I thought that I was pretty good at working my system. :rolleyes:
 
Originally posted by stoid
Okay, I changed my Terminal preferences to the "Execute the default login shell using /usr/bin/login" selection, but I don't know how to access the .login file as mentioned by zimv20. Is this through the Finder? Where is the goto bar? I am in Panther if that makes difference.

And I thought that I was pretty good at working my system. :rolleyes:

When you open Terminal and folding starts automatically, what happens if you just hit Ctrl-C? Does the terminal window just close?
 
AHHHH!! YAY!!!
pressing ctrl-c does halt the folding, and let me enter commands, so I can access my terminal now as normal, but I would still like to be able to open a new terminal window and not have to press ctrl-c. Also I would like to try out mc68k scripts again in hopes that I will get a gromacs WU instead of all these dang tinker WUs.
 
Originally posted by stoid
AHHHH!! YAY!!!
pressing ctrl-c does halt the folding, and let me enter commands, so I can access my terminal now as normal, but I would still like to be able to open a new terminal window and not have to press ctrl-c. Also I would like to try out mc68k scripts again in hopes that I will get a gromacs WU instead of all these dang tinker WUs.

Good, now (some of these may not exist) cat .cshrc, cat .tcshrc, and cat .bashrc, and make sure there is nothing in these that starts folding.

.bashrc is a startup for your bash shell.
.cshrc and .tcshrc is for your csh/tcsh.
 
I had terminal running a program whenever I opened a new terminal. I figured out how to fix it. Go to ~/Library/Preferences/com.apple.terminal.plist and then you should be able to find the evil startup commands in there.

Alexander the Great
 
AlexanderDGreat said:
I had terminal running a program whenever I opened a new terminal. I figured out how to fix it. Go to ~/Library/Preferences/com.apple.terminal.plist and then you should be able to find the evil startup commands in there.

Alexander the Great

I know this thread is really old, but I was having the same problem on 10.3.2 and I was really frustrated until I removed an execution string for fah4 from my ~/Library/Preferences/com.apple.terminal.plist

Now I'm using mc68k's scripts on a few dual G5's.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.