I'm trying to build ganglia-monitor-core-2.5.6 on Solaris 9/SPARC using gcc
3.3.1.
The gmond binary exhibits this strange behavior:
1. If /etc/gmond.conf does not exist, then running ./gmond as root works as
expected. It daemonizes itself and continues running indefinitely
(of course with the default configuration).
2. If /etc/gmond.conf exists at all, then running ./gmond as root starts,
daemonizes itself, and then disappears immediately.
3. If /etc/gmond.conf is just a zero-byte file, or running
./gmond --conf=/dev/null, then the same behavior as (2).
4. If /etc/gmond.conf exists, then running ./gmond -d1 or ./gmond -d2 works!
The process stays in the foreground, but it reads /etc/gmond.conf
properly and starts multicasting the proper data.
I don't know if this makes a difference or not, but I'm doing this on
a Solaris 9 system that I'm trying to incorporate into an existing Linux-only
Ganglia environment.
Has anyone experienced this behavior, too? Any advice on what to try next?
Thanks!
=====
--
John Saalwaechter <[EMAIL PROTECTED]>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
