linux client

[dleclair]

I've used the command 'nohup' with success to do what you're trying to do.

For example, 'nohup nfsnetclient &'.

By default, stdout is then written to nohup.out in the same directory.

Hope this helps!

Don Leclair
don@nfsnet.org

[junky]

it works thanks, Don.

The only problem is in linux, when it starts, when i pressed enter, its stops the nohup and after, i was getting an IDLE. A friend is always getting an IDLE too :(

gonna try it tomorrow morning.

[xilman]

Originally Posted by junky

when im typing:

cpatry@lespac:~/NFSNET$ ./nfsnetclient > output.txt &
[1] 11788
23:12:50 NFSNET Clientcpatry@lespac:~/NFSNET$  - V 1.0
23:12:50 Initializing...
23:12:50 Initialized.
23:12:50 Submitting results...
23:12:51 Results successfully submitted...
23:12:51 Requesting assignment...
23:12:51 Received assignment (Fenland  10_223P_2  26941353-26941392)...
23:12:51 Building .in file...
23:12:51 Updating project .in file with assigned range...
23:12:51 Launching siever...

The problem is i wanna that output into a file named output.txt .
after this: if im typing:

cpatry@lespac:~/NFSNET$ cat output.txt 
cpatry@lespac:~/NFSNET$ ls -l
total 388
drwxr-xr-x    4 cpatry   cpatry       4096 Jan 30 09:15 Deutsch
drwxr-xr-x    4 cpatry   cpatry       4096 Jan 30 09:15 English
-rw-r--r--    1 cpatry   cpatry       2656 Jan 30 09:15 README.txt
drwxr-xr-x    3 cpatry   cpatry       4096 Jan 30 09:15 UserManual
-rwxr-xr-x    1 cpatry   cpatry     143858 Jan 30 09:15 linesiever
-rwxr-xr-x    1 cpatry   cpatry      68551 Jan 30 09:15 nfsnetclient
-rwxr-xr-x    1 cpatry   cpatry      61826 Jan 30 09:15 nfsnetinit
-rw-r--r--    1 cpatry   cpatry          0 Mar 23 17:12 output.txt
drwxr-xr-x    3 cpatry   cpatry       4096 Mar 23 09:00 processors
drwxr-x---    4 cpatry   cpatry       4096 Mar 23 09:04 projects
-rwxr-xr-x    1 cpatry   cpatry      71381 Jan 30 09:15 rootfinder
cpatry@lespac:~/NFSNET$

im getting nothing in my file output.txt

It looks like the output is throw the console and not in the file.

Is there any way to fix this ?

Thanks.

Yes. The text is coming out on stderr and not stdout. You need to redirect stderr to an output file. The exact syntax is operating system and shell dependent but "2>" or ">&" are common idioms.

Paul

[junky]

why not printing the info to stdout reather then the stderr ?

[Wacky]

Originally Posted by junky

why not printing the info to stdout reather then the stderr ?

Because,
(1) stdout is involved in the stream for the real data. Using it for info gets tricky when you combine the programs in a different fashion than the one we happen to use.

(2) using stderr is the "Unix way" to handle this kind of info.

[junky]

it's the first distributed i saw running in tha way. But with the nohup, its working fine too.

[stef]

<code>
stef@heberge:~/NFSNET$ nohup ./nfsnetclient &
[1] 31308
stef@heberge:~/NFSNET$ nohup: appending output to `nohup.out'

stef@heberge:~/NFSNET$ ls
Deutsch README.txt linesiever nfsnetclient nohup.out projects
English UserManual log.txt nfsnetinit processors rootfinder
stef@heberge:~/NFSNET$ ll
total 363
drwxr-xr-x 4 stef stef 136 Jan 30 10:15 Deutsch
drwxr-xr-x 4 stef stef 168 Jan 30 10:15 English
-rw-r--r-- 1 stef stef 2656 Jan 30 10:15 README.txt
drwxrwxr-x 3 stef stef 72 Jan 30 10:15 UserManual
-rwxrwxr-x 1 stef stef 143858 Jan 30 10:15 linesiever
-rw-r--r-- 1 stef stef 743 Mar 15 13:04 log.txt
-rwxrwxr-x 1 stef stef 68551 Jan 30 10:15 nfsnetclient
-rwxrwxr-x 1 stef stef 61826 Jan 30 10:15 nfsnetinit
-rw------- 1 stef stef 430 Mar 24 22:04 nohup.out
drwxrwxr-x 3 stef stef 104 Mar 15 13:05 processors
drwxr-x--- 4 stef stef 104 Mar 15 13:06 projects
-rwxrwxr-x 1 stef stef 71381 Jan 30 10:15 rootfinder
[1]+ Segmentation fault nohup ./nfsnetclient
</code>

I don't understand why I still get "Segmentation fault" after running the client... Any idea?


Stéphane

[junky]

and on my new linux box, im getting this problem:

19:19:14 Received assignment (Longhorn  10_223P_2  27807125-27807132)...
19:19:14 Building .in file...
19:19:14 Updating project .in file with assigned range...
19:19:14 Launching siever...
decread_slong:  Illegal characters in input
19:19:19 Siever finished...
19:19:19 Submitting results...
19:19:20 Results successfully submitted...
19:19:20 Requesting assignment...
19:19:20 Received assignment (  IDLE  0-0)...

The problem is im getting a "decread_slong" and after, im blacklisted for 6 hours, i've got it twice in about 24 hours, so its 12 hours of CPU wasted.

Any solution to solve this ?

[junky]

stef: do ya think its caused by nfsnetclient or maybe it could be caused by the nohup's program ?

[junky]

i've saw this in my nohup.out:

...
12:24:34 Launching siever...
Erroneous divisors in check_cofactor_status
aout = 2668039, bout = 12125895, polynomial 1
abs(norm) = 226971656489343434280089631059411856769087801
Product of divisors = 405563936974238264535132056100225
Quotient = 559644573387
Remainder = 243705115034399649493285729375726
Divisor 1 = 22727
Divisor 2 = 114419
Divisor 3 = 3826741
Divisor 4 = 19518307
Divisor 5 = 31165425
Divisor 6 = 67
12:33:46 Siever finished...
12:33:46 Submitting results...
12:33:47 Results successfully submitted...
12:33:48 Requesting assignment...
12:33:48 Received assignment (  IDLE  0-0)...

and now im blacklisted from server, this box is always banned from server.
i really appreciate if someone can help me, and keep my machine crunching, cause im wasting my cpu cycle now

Thanks in advance.

[dleclair]

That message usually indicates hardware problem, unfortunately. I saw it quite often when I had a stick of RAM that had several bad bits on it.

Unlike other distributed apps, the NFSNET client exercises a large block of RAM quite intensely and so it is somewhat more vulnerable to RAM errors.

If you're running on an Intel-architecture box you might try Memtest86(http://memtest86.com) to see if there actually is a problem. It's a free OS-independent memory tester that has served me well many times.

Don Leclair