From owner-freebsd-questions Sun Nov 24 14:13:45 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A0A37B401 for ; Sun, 24 Nov 2002 14:13:44 -0800 (PST) Received: from pohoda.cz (pohoda.pohoda.cz [194.228.111.151]) by mx1.FreeBSD.org (Postfix) with SMTP id BA5F743E91 for ; Sun, 24 Nov 2002 14:13:42 -0800 (PST) (envelope-from plusik@pohoda.cz) Received: (qmail 22010 invoked from network); 24 Nov 2002 22:13:49 -0000 Received: from plusik@pohoda.cz by pohoda.cz by uid 513 with qmail-scanner-1.15 ( Clear:. Processed in 3.056318 secs); 24 Nov 2002 22:13:49 -0000 Received: from saturn.netcore.cz (HELO localhost.localdomain) (212.67.74.6) by pohoda.pohoda.cz with SMTP; 24 Nov 2002 22:13:45 -0000 Received: by localhost.localdomain (Postfix, from userid 1000) id E513E1CB910; Sun, 24 Nov 2002 23:13:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id E265E1CB6CD; Sun, 24 Nov 2002 23:13:34 +0100 (CET) Date: Sun, 24 Nov 2002 23:13:34 +0100 (CET) From: Tomas Pluskal X-X-Sender: plusik@localhost.localdomain To: Kent Stewart Cc: freebsd-ports@FreeBSD.ORG, Subject: Re: setiathome port: Can't open file temp.sah In-Reply-To: <3DE14C9D.40305@owt.com> Message-ID: <20021124231001.K17805-100000@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, this is a non-working seti :) [root@eddie tmp]# l /tmp/seti total 320 -rw-r--r-- 1 plusik wheel 0 24 lis 22:53 lock.sah -r-xr-xr-x 1 plusik wheel 299008 24 lis 22:24 setiathome The /tmp/seti dir has these permissions: drwxr-xr-x 2 plusik wheel 512 24 lis 22:53 seti There are no .sah files, because I was unable to login to seti@home. (Of course I've tried to remove lock.sah, create new fresh dir etc.) I've tried to connect to the seti@home server manually and there is no problem with connection. Tomas > > This is a working seti > > drwxr-xr-x 2 seti staff 512 Nov 21 10:43 ruby3 > > ruby#seti>cd ruby3 > ruby#seti>ll > total 675 > -rw-r--r-- 1 seti staff 132 Nov 24 14:00 key.sah > -rw-r--r-- 1 seti staff 0 Apr 10 2000 lock.sah > -rw-r--r-- 1 seti staff 828 Nov 24 13:11 outfile.sah > -rw-r--r-- 1 seti staff 6 Nov 24 12:48 pid.sah > -rw-r--r-- 1 seti staff 160 Nov 21 10:43 result_header.sah > -rwxr-xr-x 1 seti staff 299008 Dec 26 2000 setiathome > -rw-r--r-- 1 seti staff 4065 Nov 24 14:00 state.sah > -rw-r--r-- 1 seti staff 405 Apr 10 2000 temp.sah > -rw-r--r-- 1 seti staff 366 Nov 21 10:43 user_info.sah > -rw-r--r-- 1 seti staff 32 Dec 27 2000 version.sah > -rw-r--r-- 1 seti staff 356282 Nov 21 10:43 work_unit.sah > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message