Yeah...you're right! :) I kind-a wondered if there wasn't something going
on with the command and that'll do it everytime.
anytime you want to modify the command line syntax you will have to stop
the current process to do it. The easiest way to stop the process is just
to hit CTRL-C. That will Cancel the process all together. However, it's
been my experience that you very may well have to kill the process through
Process Management (kpm). For some reason the Linux binary seems to favor
process-runon when trying to shut it down sometimes. Not always mind you,
but sometimes.
--
Mark
/* I never worry about the to-jams.
* Once I've stuck my foot in my mouth
* it's already too late...just make sure
* you chew them thoroughly before swallowing!
*/
Registered Linux user #182496
* Pine 4.21 *
On Thu, 5 Oct 2000 8:58am ,Dennis Myers spake passionately in a message:
> Mark Weaver wrote:
> >
> > I run Seti@home constantly and there's nothing wrong at all. Mine is an
> > AMD K6-233. So what's your point?
> >
> > What I'd like to know is the command that he's using to start the
> > program. Everything about Seti@home comes ready to go right out-a the
> > box. All you have to do is untar it to it's home and call it from the
> > command line. There isn't any configuring or compiling that needs to be
> > done.
> >
> > Example: (to call and start the program place the setiathome binary in
> > it's own directory - open a terminal window - navigate to that dir and
> > issue this command)
> >
> > ./setiathome -verbose -nice 19 <ENTER>
> >
> > that's ALL there is to it. I'm not trying to be rude here but it's not
> > rocket science. They've made it as simple as possible for very good
> > reason. They REALLY want EVERYONE to be able to use this program to crunch
> > the numbers for them.
> >
> > --
> > Mark
> >
> > /* I never worry about the to-jams.
> > * Once I've stuck my foot in my mouth
> > * it's already too late...just make sure
> > * you chew them thoroughly before swallowing!
> > */
> > Registered Linux user #182496
> > * Pine 4.21 *
> >
> > On Wed, 4 Oct 2000 10:29pm ,Bob spake passionately in a message:
> >
> > > Are you by any chance using an AMD processor?
> > >
> > > At 06:18 PM 10/4/00 -0500, you wrote:
> > > >Ed Tharp wrote:
> > > > >
> > > > > which "3" are you hitting (top of qwerty keys or numbers pad? and is
> > > > the num
> > > > > lock light on?
>
> Not rocket science, but when you forget the . in front of the slash, it
> don't work right. I didn't put the verbose command in, can you add it
> somehow without restarting the work unit? Anyway it seems to be running
> now.
>
