Date: Wed, 27 Mar 2002 15:17:27 +1100 From: Rob B <rbyrnes@ozemail.com.au> To: freebsd-alpha@freebsd.org Subject: Re: Seti not working on 4.5-STABLE Message-ID: <5.1.0.14.2.20020327150951.00a78020@pop.ozemail.com.au> In-Reply-To: <20020319082257.GB12319@cicely8.cicely.de> References: <5.1.0.14.2.20020314152904.01c3f940@pop.ozemail.com.au> <5.1.0.14.2.20020314152904.01c3f940@pop.ozemail.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
At 19:22 19/03/2002, Bernd Walter sent this up the stick: >On Tue, Mar 19, 2002 at 02:07:05PM +1100, Rob B wrote: > > Hi all, > > > > I'm trying to get the OSF1 client running, <snip> > > I do have the osf1 module loaded: > > > > erwin# kldstat > > Id Refs Address Size Name > > 1 3 0xfffffc0000300000 2dda68 kernel > > 2 1 0xfffffe0000b70000 20000 osf1.ko > > 3 1 0xfffffe0000b96000 28000 linux.ko > > > > I also get a similar result with the Linux client. Do I need any special > > magic to get it to work? > >You may want to check your /etc/resolv.conf and /etc/hosts. >AFAIK the osf1 libs are more sensible about propper syntax. Continuing on my little setiathome thread, I'm running it from cron thus: [root@erwin]/root: crontab -l # Run setiathome, and check it every hour 0 * * * * cd /usr/local/bin/seti-tru; ./setiathome > /dev/null 2> /dev/null This is as suggested on the seti website. the issue with this is that the lockfile (lock.sah) is not being respected by the client, and cron ends up starting the setiathome process every hour. Is there a way to test whether the client is running, and not start a new process of it if there is one? Cheers, Rob -- We should build an Intel processor out of penguins. [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian This is random quote 1124 of a collection of 1223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.1.0.14.2.20020327150951.00a78020>