Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Community > Team MacNN > Can you tie the F@H screensaver into the cli app?

Can you tie the F@H screensaver into the cli app?
Thread Tools
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 11, 2003, 10:26 AM
 
I want to run the cli app so that it can be running all the time in the background at a low level of cpu usage, but I also want the screensaver so that I get a little graphical reward once in a while to remind me of my good deeds. Is it possible to run the cli app and have the screensaver tie into the cli and just 'report' what it is doing? In other words, instead of having the SS use its own engine, etc can it just use the cli version and give a real time update of what is happening in the cli whenever the SS kicks in?

I hope that was clear.

kman
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 11, 2003, 10:40 AM
 
Oh yeah. Is there a way to get it to run when no one is logged in?

kman
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 11, 2003, 06:52 PM
 
And why doesn't the screensaver recognize the password protection? Very annoying.

kman
     
Administrator
Join Date: May 2000
Location: California
Status: Online
Reply With Quote
Mar 11, 2003, 07:16 PM
 
There is no known way to make the SS and CLI share the same work unit without launching two crunching cores on it. You can make them share the same work folder, but you would have to manually kill one before enabling the other, the clients do not have collision detection.

The SS will run if everyone is logged out. The CLI will keep running after a logout if launched with the " &" tag. ie: "./folding &"

The F@H SS does not honor Saver Password protection. This is a known bug which has been posted to the Folding/Genome forums for the development team to fix. It should be noted that there are known ways around Saver Password protection anyway, bugs that Apple is working on. Do not depend on Saver Password protection for serious security at this time.
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 11, 2003, 08:14 PM
 
Originally posted by reader50:

The SS will run if everyone is logged out. The CLI will keep running after a logout if launched with the " &" tag. ie: "./folding &"
I just want to clear one thing up: the SS will really run after log out? Other SSs don't do that? Is there anything funny about this?

Thanks for all the info!!

kman
     
Administrator
Join Date: May 2000
Location: California
Status: Online
Reply With Quote
Mar 12, 2003, 01:22 AM
 
I misremembered. The SETI SS will run at Logout, the Folding SS is a normal SS and will not run at Logout.

However, you could cron either the GUI or CLI client, which will cause it to start up on schedule, even if everyone is logged out. And of course, you can launch the CLI client with the " &" tag.
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 12, 2003, 08:32 AM
 
Originally posted by reader50:
I misremembered. The SETI SS will run at Logout, the Folding SS is a normal SS and will not run at Logout.

However, you could cron either the GUI or CLI client, which will cause it to start up on schedule, even if everyone is logged out. And of course, you can launch the CLI client with the " &" tag.
Does the "&" tag force it to run in root or anything funny that may be a security concern? I want to set it up on a couple of our lab machines, but I don't want to compromise their security.

kman
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 12, 2003, 09:11 AM
 
I'm trying to launch the cli and it keeps stopping at this point:
Writing "work/wudata_01.xyz": (overwrite)

It never says successful and continues as I have seen it do in the past.

kman
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 12, 2003, 10:58 AM
 
Okay, last question!

I setup two folding directories, one for each processor. I assigned machine ID 1 to one and ID 2 to the other. I want them both to run when no one is logged in and I want the process to start when I log in (so it basically runs all the time as long as I have logged in at some point after the machine starts up). Several questions:

1) does using the "&" flag run the processes as root or as my user? Are there any security concerns here?

2) I set up two 'command' files as follows:

cd documents/folding
./osx-3.24 -local &

AND
cd documents/folding2
./osx-3.24 -local &

I then set both of these commands to run on login using the Login prefs pane. This seems to get things running fine. If I log in multiple times (thus executing the commands) will it screw things up or will know that it is already running and just carry on normally?

thanks,
kman
     
kman42  (op)
Professional Poster
Join Date: Sep 2000
Location: San Francisco
Status: Offline
Reply With Quote
Mar 12, 2003, 11:04 AM
 
Originally posted by kman42:
Okay, last question!

I setup two folding directories, one for each processor. I assigned machine ID 1 to one and ID 2 to the other. I want them both to run when no one is logged in and I want the process to start when I log in (so it basically runs all the time as long as I have logged in at some point after the machine starts up). Several questions:

1) does using the "&" flag run the processes as root or as my user? Are there any security concerns here?

2) I set up two 'command' files as follows:

cd documents/folding
./osx-3.24 -local &

AND
cd documents/folding2
./osx-3.24 -local &

I then set both of these commands to run on login using the Login prefs pane. This seems to get things running fine. If I log in multiple times (thus executing the commands) will it screw things up or will know that it is already running and just carry on normally?

thanks,
kman
I guess I answere the second question all on my own as I now have about 10 osx-3.24 and fahcore processes running after logging in and out a few times. Looks like I will be launching manually.

I'm still interested in the security question if anyone has an answer to that.

thanks,
kman
     
Forum Regular
Join Date: Nov 2002
Location: Santa Barbara CA
Status: Offline
Reply With Quote
Mar 12, 2003, 12:03 PM
 
Originally posted by kman42:
Okay, last question!

I setup two folding directories, one for each processor. I assigned machine ID 1 to one and ID 2 to the other. I want them both to run when no one is logged in and I want the process to start when I log in (so it basically runs all the time as long as I have logged in at some point after the machine starts up). Several questions:

1) does using the "&" flag run the processes as root or as my user? Are there any security concerns here?

2) I set up two 'command' files as follows:

cd documents/folding
./osx-3.24 -local &

AND
cd documents/folding2
./osx-3.24 -local &

I then set both of these commands to run on login using the Login prefs pane. This seems to get things running fine. If I log in multiple times (thus executing the commands) will it screw things up or will know that it is already running and just carry on normally?

thanks,
kman
The "&" just means to run in the background, it doesn't tie up the terminal.

Yes, as you have found out you do not want to launch multiple times.

But even when running normally a lot of processes show up. I am running top on a dual proc linux box and I see 6 instances of FahCore_65.exe and 10 instances of folding (which is what I renamed what you know as osx-3.24). But there are only two FahCore_65.exe that are using the processors, that is what you need to look for.

If you want to stop it, you need to kill the oldest osx-3.24 process.
     
Senior User
Join Date: Feb 2002
Location: Silly Valley, Ca
Status: Offline
Reply With Quote
Mar 13, 2003, 02:04 AM
 
If you don't nohup the process(es) when you start them, they should die when you log out.
If they are not that is very odd, unless you are still logged in on the console and loging in and out via Terminal, ssh, etc.

The linux ps thing is an absurdity and annoyance. On OS X, you should only see one OSX-3.24 and one FAHCore_65 process for each instance you run.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 09:12 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2