[Spread-users] How do you verify if spread is running.

[Theo Schlossnagle]

In the spread configuration file you can specify a file to log to...  I 
always use:

EventLogFile = /var/log/spread/mainlog

Specify a legitimate full path to a log file and start up spread.  Then, 
if you spuser fails to connect, look in that file to see what the error 
might be.

If you are running Spread and it is returning you to the command line, 
then there is a problem an you should check the log file.  As Spread, 
without patching, does not daemonize.  The freebsd version of Spread 
(from ports) incorporates a patch to fork/setsid/fork so that Spread can 
run as a daemon.  You should consider patching your source code with 
that patch (it can be fetched from the FreeBSD ports tree).  That is the 
one truly worthwhile patch to Spread -- necessary in my opinion.


On Thursday, July 11, 2002, at 06:28 PM, Tim Clashin wrote:

> I am running spread on Solaris 9.  I created a sample.conf file, and 
> when I run ./spread -c spread.conf, I get the following:
>
> ip_init: using file: spread.access_ip
> Conf_init: using file: /etc/spread.conf
> Successfully configured Segment 0 [127.0.0.255:4803] with 1 procs:
>                    localhost: 127.0.0.1
>
> I am just trying to get spread running on my test box.  My question 
> here is when I use the spuser command, I get the following error:
>
> Spread library version is 3.16.2
> SP_error: (-2) Could not connect. Is Spread running?
>
> Bye.
>
> What process do I check for to see if the spread daemon is running?
>
> Tim Clashin
>
>  
>

>

>
> Join the worldís largest e-mail service with MSN Hotmail. Click Here
>
--
Theo Schlossnagle
Principal Consultant
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
Phone:  +1 301 776 6376       Fax:  +1 410 880 4879
1024D/82844984/95FD 30F1 489E 4613 F22E  491A 7E88 364C 8284 4984
2047R/33131B65/71 F7 95 64 49 76 5D BA  3D 90 B9 9F BE 27 24 E7