March 2011 - Xymon - Xymon mailman web

Xymon mailing list now on a new server (but hopefully everything works!)
by henrik＠hswn.dk 14 Mar '11

14 Mar '11

Just to let you know that everything has been moved, and hopefully it should be running as usual. Regards, Henrik

5 11

LFS support check failed for standard file support - xymon 3.0
by vadud3＠gmail.com 14 Mar '11

14 Mar '11

# uname -a SunOS solaris 5.10 Generic_142910-17 i86pc i386 i86pc # MAKE=gmake ./configure.client [..] Checking for clock_gettime() requiring librt ... clock_gettime() requires librt Is this means librt is missing? Checking for Large File Support ... ERROR: LFS support check failed for standard file support I am pretty sure solaris 10 x86 supports large file system. -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

4 9

Custom Graphs using SPLITNCV -- '/' character conversion issue in variable names
by consta＠gmail.com 14 Mar '11

14 Mar '11

Hi guys, I'm using Xymon 4.3.0-0.20110123.rc1 and I recently added a custom graph which is drawing the inode usage on all mounted partitions, grabbing the data from the output of "df -i" command. All goes well, I get the graph drawn, as I send the data in this format: --- cut here --- /:10 /tmp:1 --- and here --- The following RRD files are created: - inodes,.rrd - inodes,_tmp.rrd The GPRINT shows the following strings on the graph: - / - /_tmp I know that all the non-word and digit characters are stripped from the NAMES, but the problem is that it doesn't put them back while displayed on the .PNG image. The trick I did was to strip the leading '/' from all the partitions except for /. This works fine for partitions mounted directly under /, but if you mount it deeper, you get back to the same problem: NAME: a/b/c gets translated to /a_b_c Does anyone know to solve this issue? Thanks in advance! //Sorin

1 1

downtime syntax revisited
by tm＠freedom.com 14 Mar '11

14 Mar '11

Betsy provides an example of downtime with only three fields, which appear to be day, start time, end time. >From the docs: DOWNTIME=[columns:]day:starttime:endtime:cause[,day:starttime:endtime:cause] >From my working config (4.2.0): "DOWNTIME=*:*:2200:0730:Nightly Reboot" With Betsy's exclusion of the [optional] Columns, does that specify ALL services for that host? (To think, I've been using an extra wildcard for a couple of years :/ ) Maybe this has changed in some new version, if so disregard. I have not looked a 4.3 yet but it's on the schedule. Thanks and Regards, Tim ________________________________________ From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Elizabeth Schwartz [betsy.schwartz@] Sent: Monday, March 14, 2011 9:43 AM To: Henrik Størner Cc: xymon at xymon.com Subject: Re: [Xymon] Newbie badhttp questions Great thanks! I note that this one DOES work: ################# set a new default 0.0.0.0 .default. # DOWNTIME=0:0000:0300 badhttp:::2

2 1

LFS support on Solaris
by soopal＠ice.go.cr 14 Mar '11

14 Mar '11

Hi all; I have comment this behavior before to Henrik. The script expects some different numbers that the program output. For example on Solaris 10 32bits the last number that program returns is the maximum value for an int so is 32,767 and the negative sign; as I talked to Henrik looks to me an endiannes issue about that calculation (I guess). Since the value on Solaris Sparc (64bits) is really different. --- Since I modify the lfs.sh script to let the installation continue I have no dedicate time to really diagnose/correct the issue. ________________________________ Este mensaje de correo electr?nico, incluidos los archivos adjuntos, es para el uso exclusivo de la persona a la que se ha enviado, y puede contener informaci?n que sea confidencial o protegida legalmente. Si usted no es el destinatario, o ha recibido este mensaje por error, no est? autorizado a copiar, distribuir, o utilizar de alguna manera este mensaje. Por favor notifique inmediatamente al remitente por correo electr?nico y suprimir permanentemente este mensaje y los archivos adjuntos. No se otorga ninguna garant?a de que este e-mail est? libre de errores o virus. INSTITUTO COSTARRICENSE DE ELECTRICIDAD

1 0

Newbie badhttp questions
by betsy.schwartz＠gmail.com 14 Mar '11

14 Mar '11

Pile of beginner questions here: 1) if I have two http tests for one server, as in 10.0.1.2 myserver.example.com # http://myserver.example.com/link1 http://myserver.example.com/link2 do I need to put a separate badhttp after each test or can I just put one at the end? 2) If a network test fails it is repeated at short intervals, IIRC it's every minute. If I set badhttp:1:2:4 , is it counting four 1-minute intervals or four 5-minute xymon test intervals? 3) Is there a way to set a default for all http tests and just override for a few servers? We'll want almost all our servers to wait a few minutes before alerting and 4) do I need a trailing / on the url? thanks much Betsy

3 5

failing to compile on solaris 7 (was Re: Xymon 4.3.0 released)
by vadud3＠gmail.com 14 Mar '11

14 Mar '11

On Fri, Mar 4, 2011 at 5:46 AM, Henrik Størner <henrik at hswn.dk> wrote: > I am pleased to announce the release of version 4.3.0 of the Xymon > monitoring software. > > The previous release happened two years ago, so I can understand why people > started worrying if Xymon was dead. Fortunately, that is not the case - and > thanks for being so patient with this release. > > I would like to thank everyone involved in the development - those who have > contributed code and patches, as well as all of the users who took time to > report bugs, make suggestions for improvements or fix documentation. > > Also, a big "Thank You" should be given to the people here on the Xymon > mailing list, who take time off from their active admin duties to help > answer questions from newbies and experts alike. Without you, Xymon would > never have become as popular as it is. > > Xymon 4.3.0 is available from Sourceforge at > https://sourceforge.net/projects/xymon/ > The sourcecode file is currently being mirrored out from the master sf.net > site, but should be available soon. For verification, the xymon-4.3.0.tar.gz > file should look like this: > > Size: 2679880 bytes > MD5: 5972786d7102403674c12d97380d00e1 > SHA-1: 839a6d64e53101fa3e4381ce17a669292c691ebd > > > Regards, > Henrik > > PS: Bug reports to xymon at xymon.com, please! failing to compile on solaris 7 # ./configure.client Configuration script for Xymon client This script asks a few questions and builds a Makefile to compile Xymon Checking your make-utility Xymon normally keeps all of the client configuration files on the Xymon server. If you prefer, it is possible to use a local client configuration file instead - if so, answer 'client' to the next question. NB: Local configuration requires the PCRE libs on each host. Server side client configuration, or client side [server] ? Checking for Large File Support ... ERROR: Compiler doesnt recognize the off_t C type. Checking for clock_gettime() requiring librt ... clock_gettime() not present, but this should be OK [..] # gmake -s Checking for socklen_t Checking for snprintf Checking for vsnprintf Checking for rpc/rpcent.h Checking for sys/select.h Checking for u_int32_t typedef Checking for PATH_MAX definition Checking for SHUT_RD/WR/RDWR definitions Checking for strtoll() config.h created ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a165d is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1661 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1665 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a17a5 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a181d is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1821 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1bb7 is non-aligned collect2: ld returned 1 exit status gmake[1]: *** [test-endianness] Error 1 gmake: *** [lib-client] Error 2 > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

3 2

LFS support check failed for standard file support - xymon 3.0
by henrik＠hswn.dk 14 Mar '11

14 Mar '11

> MAKE="gmake" sh -x ./build/lfs.sh > + echo Checking for Large File Support ... > Checking for Large File Support ... > + cd build > + gmake -f Makefile.test-lfs clean > + uname -s > + tr [/] [_] > OS=SunOS > gmake: *** [clean] Error 2 > + gmake -f Makefile.test-lfs > gmake: Nothing to be done for `all'. > + [ 0 -ne 0 ] > + ./test-lfs-std 4 > STDRES=4:1:-78191077919555584 > + test 4:1:-78191077919555584 != 4:1:0 -a 4:1:-78191077919555584 != 8:1:0 > + echo ERROR: LFS support check failed for standard file support > ERROR: LFS support check failed for standard file support > + exit 1 This is bizarre. What this does is that it builds a tiny test program using standard compiler-flags first, and then the flags that you would normally use when compiling for large file support (LFS). When compiled without LFS, I expect the normal file offset "off_t" variable to be 32 bits (4 bytes); with LFS, I would expect it to be 64-bits (8 bytes). To test that, the program prints out 1) The value of "sizeof(off_t)" 2) A boolean (0/1) value to see if sizeof(off_t) is what I expect 3) The value of an off_t variable that has been cleared to zero using memset() - we need to print these values occasionally (e.g. for keeping track of how long into a logfile we have already scanned). 1) and 2) look OK, but the value prints as "-7819...." There is no way I can see how that can happen - that variable has been cleared to 0 just a few lines above the print-statement. Just to see if I'm completely wrong, could you try running this for me: cd build rm test-lfs-std test-lfs-lfs OS=SunOS gmake -f Makefile.test-lfs ./test-lfs-std 4 ./test-lfs-lfs 8 The output from the last line would be interesting. Thanks, Henrik

2 1

Zymon 4.2.3 libssl error (64bit)
by skoupi＠gmail.com 14 Mar '11

14 Mar '11

Thanks for the reply Ralph. Does anyone have an idea regarding the error message ? On Sat, Mar 12, 2011 at 17:50, Ralph Mitchell <ralphmitchell at gmail.com>wrote: > On Sat, Mar 12, 2011 at 11:39 AM, Nick Gr <skoupi at gmail.com> wrote: > >> Hi, >> >> I tried to install Zymon 4.2.3 in a Centos 64 bit and get the following >> message when I run make install : >> >> etcfiles; (echo "bb-hosts"; echo "hobbit-alerts.cfg"; echo >> "hobbit-clients.cfg"; echo "bbcombotest.cfg"; echo "client-local.cfg") | >> ../../build/setup-newfiles /home/xymon/server/etc/ >> ../../build/setup-newfiles: error while loading shared libraries: >> libssl.so.6: cannot open shared object file: No such file or directory >> make[1]: *** [install-cfg] Error 127 >> make[1]: Leaving directory `/home/xymon/xymon-4.2.3/hobbitd' >> make: *** [install-hobbitd] Error 2 >> >> >> It seems the installation needs the openssl and openssl-devel 32 bit >> instead of 64, I have tried to create a symbolic link to the 64 version but >> it confirms the error with a message regarding ELF-64.. >> >> Can some one please tell me if Xymon is official compatible with 64 bit >> systems and if yes how can I proceed with this problem ? >> > > I have a 64-bit system with Fedora 14: > > Linux lorien.example.com 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 > 07:06:44 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux > > and have built both xymon-4.2.3 & xymon-4.3.0 without a problem. I have: > > openssl-devel-1.0.0d-1.fc14.x86_64 > openssl-1.0.0d-1.fc14.x86_64 > > as well as rrdtool, openldap & pcre devel rpms. > > Ralph Mitchell > >

2 2

Xymon Digest, Vol 2, Issue 26
by balothia＠rediffmail.com 14 Mar '11

14 Mar '11

Hi All, I am new to Xymon and customizing it for my environment. Till now starting customizing from HTML Pages till adding additional scripts I have customized these all things. Its a very good experience working with Xymon. I am looking for some custome graphs. Do you guys have some links or document for custom graphs. Thanks, Gautam On Mon, 14 Mar 2011 16:38:59 , xymon-request at xymon.com wrote Send Xymon mailing list submissions to    xymon at xymon.com To subscribe or unsubscribe via the World Wide Web, visit    http://lists.xymon.com/mailman/listinfo/xymon or, via email, send a message with subject or body 'help' to    xymon-request at xymon.com You can reach the person managing the list at    xymon-owner at xymon.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Xymon digest..." Today's Topics:   1. failing to compile on solaris 7 (was Re: Xymon 4.3.0      released) (Asif Iqbal)   2. xymon 3.0 client - failing to compile on solaris 8 (Asif Iqbal)   3. make: Fatal error: Command failed for target      `rrdtoolmodule.o' [Sun Solaris 5.10] (Jayanta Kundu)   4. xymon 4.3.0-RC1 Oversize notes/user msg (Kapildev Khemraj)   5. Re: make: Fatal error: Command failed for target      `rrdtoolmodule.o' [Sun Solaris 5.10] (Henrik St?rner)   6. Re: xymon 4.3.0-RC1 Oversize notes/user msg (Henrik St?rner)   7. Re: xymon 3.0 client - failing to compile on solaris 8      (Henrik St?rner)   8. Re: failing to compile on solaris 7 (was Re: Xymon 4.3.0      released) (Henrik St?rner)   9. Re: xymon 4.3.0-RC1 Oversize notes/user msg (Kapildev Khemraj)  10. Re: xymon 3.0 client - failing to compile on solaris 8      (Asif Iqbal)  11. LFS support check failed for standard file support - xymon      3.0 (Asif Iqbal)  12. Re: xymon 4.3.0-RC1 Oversize notes/user msg (Henrik St?rner)  13. Re: LFS support check failed for standard file support -      xymon   3.0 (Henrik St?rner)  14. Re: xymon 4.3.0-RC1 Oversize notes/user msg (Kapildev Khemraj) ---------------------------------------------------------------------- Message: 1 Date: Sun, 13 Mar 2011 15:56:06 -0400 From: Asif Iqbal <vadud3 at gmail.com> To: xymon at xymon.com Subject: [Xymon] failing to compile on solaris 7 (was Re: Xymon 4.3.0    released) Message-ID:    <AANLkTinrmjaer0bXZoMGpJzLNiceC39d1uXSg644POz+ at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On Fri, Mar 4, 2011 at 5:46 AM, Henrik St?rner <henrik at hswn.dk> wrote: > I am pleased to announce the release of version 4.3.0 of the Xymon > monitoring software. > > The previous release happened two years ago, so I can understand why people > started worrying if Xymon was dead. Fortunately, that is not the case - and > thanks for being so patient with this release. > > I would like to thank everyone involved in the development - those who have > contributed code and patches, as well as all of the users who took time to > report bugs, make suggestions for improvements or fix documentation. > > Also, a big "Thank You" should be given to the people here on the Xymon > mailing list, who take time off from their active admin duties to help > answer questions from newbies and experts alike. Without you, Xymon would > never have become as popular as it is. > > Xymon 4.3.0 is available from Sourceforge at > ? https://sourceforge.net/projects/xymon/ > The sourcecode file is currently being mirrored out from the master sf.net > site, but should be available soon. For verification, the xymon-4.3.0.tar.gz > file should look like this: > > Size: 2679880 bytes > MD5: 5972786d7102403674c12d97380d00e1 > SHA-1: 839a6d64e53101fa3e4381ce17a669292c691ebd > > > Regards, > Henrik > > PS: Bug reports to xymon at xymon.com, please! failing to compile on solaris 7 # ./configure.client Configuration script for Xymon client This script asks a few questions and builds a Makefile to compile Xymon Checking your make-utility Xymon normally keeps all of the client configuration files on the Xymon server. If you prefer, it is possible to use a local client configuration file instead - if so, answer 'client' to the next question. NB: Local configuration requires the PCRE libs on each host. Server side client configuration, or client side [server] ? Checking for Large File Support ... ERROR: Compiler doesnt recognize the off_t C type. Checking for clock_gettime() requiring librt ... clock_gettime() not present, but this should be OK [..] # gmake -s Checking for socklen_t Checking for snprintf Checking for vsnprintf Checking for rpc/rpcent.h Checking for sys/select.h Checking for u_int32_t typedef Checking for PATH_MAX definition Checking for SHUT_RD/WR/RDWR definitions Checking for strtoll() config.h created ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a165d is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1661 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1665 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a17a5 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a181d is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1821 is non-aligned ld: fatal: relocation error: R_SPARC_32: file /var/tmp//ccuzQGSi.o: symbol <unknown>: offset 0xff0a1bb7 is non-aligned collect2: ld returned 1 exit status gmake[1]: *** [test-endianness] Error 1 gmake: *** [lib-client] Error 2 > _______________________________________________ > Xymon mailing list > Xymon at xymon.com > http://lists.xymon.com/mailman/listinfo/xymon > -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? ------------------------------ Message: 2 Date: Sun, 13 Mar 2011 16:11:22 -0400 From: Asif Iqbal <vadud3 at gmail.com> To: xymon at xymon.com Subject: [Xymon] xymon 3.0 client - failing to compile on solaris 8 Message-ID:    <AANLkTi=HEz4cfEj+OVGxAwbWDg6MmdpfnHQE9f+u5RJK at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 gmake -s Checking for socklen_t Checking for snprintf Checking for vsnprintf Checking for rpc/rpcent.h Checking for sys/select.h Checking for u_int32_t typedef Checking for PATH_MAX definition Checking for SHUT_RD/WR/RDWR definitions Checking for strtoll() config.h created loadhosts.c: In function `xmh_find_item': loadhosts.c:226: warning: return discards qualifiers from pointer target type loadhosts.c: In function `xmh_item_id': loadhosts.c:625: warning: return discards qualifiers from pointer target type msort.c: In function `msort': msort.c:119: warning: passing arg 4 of `qsort' from incompatible pointer type sendmsg.c: In function `sendtoxymond': sendmsg.c:138: warning: 'sockfd' might be used uninitialized in this function stackio.c: In function `stackfgets': stackio.c:424: warning: 'eolchar' might be used uninitialized in this function stackio.c:440: warning: 'eolchar' might be used uninitialized in this function timefunc.c: In function `timespec_text': timefunc.c:147: warning: passing arg 2 of `getescapestring' from incompatible pointer type timefunc.c:126: warning: 'days' might be used uninitialized in this function timefunc.c:126: warning: 'starttime' might be used uninitialized in this function timefunc.c:126: warning: 'endtime' might be used uninitialized in this function timefunc.c:126: warning: 'columns' might be used uninitialized in this function Undefined                       first referenced symbol                             in file main /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.6/crt1.o ld: fatal: Symbol referencing errors. No output written to setup-newfiles collect2: ld returned 1 exit status gmake[1]: *** [setup-newfiles] Error 1 gmake: *** [build-build] Error 2 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? ------------------------------ Message: 3 Date: Sun, 13 Mar 2011 23:51:00 +0330 From: Jayanta Kundu <jayantak007 at gmail.com> To: xymon at xymon.com Subject: [Xymon] make: Fatal error: Command failed for target    `rrdtoolmodule.o' [Sun Solaris 5.10] Message-ID:    <AANLkTi=1Kv3gMvNxy-jDEV8NN3CvvUOz9qH2QPMpKkNx at mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hi All, In Sun Solaris 5.10 i am trying to install rrdtool-1.2.19. 1. #./configure              [It's success] 2. # make                    [It's giving following error:] creating rrdcgi Making all in bindings Making all in python if gcc -DHAVE_CONFIG_H -I. -I. -I../..  -g -O2 -fno-strict-aliasing -Wall -std=gnu99 -pedantic -Wshadow -Wpointer-arith -Wcast-align -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -W -fPIC -DPIC -I../../src -I/usr/sfw/include/python2.3 -D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -I/usr/include/libart-2.0 -I/usr/include/freetype2 -I/usr/sfw/include -I/usr/sfw/include/freetype2  -g -O2 -fno-strict-aliasing -Wall -std=gnu99 -pedantic -Wshadow -Wpointer-arith -Wcast-align -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline -W  -fPIC -DPIC -MT rrdtoolmodule.o -MD -MP -MF ".deps/rrdtoolmodule.Tpo" -c -o rrdtoolmodule.o rrdtoolmodule.c; \ then mv -f ".deps/rrdtoolmodule.Tpo" ".deps/rrdtoolmodule.Po"; else rm -f ".deps/rrdtoolmodule.Tpo"; exit 1; fi In file included from /usr/include/limits.h:18,                 from /usr/sfw/include/python2.3/Python.h:19,                 from rrdtoolmodule.c:42: /usr/include/sys/feature_tests.h:332:2: #error "Compiler or options invalid for pre-UNIX 03 X/Open applications         and pre-2001 POSIX applications" rrdtoolmodule.c: In function `PyRRD_fetch': rrdtoolmodule.c:202: warning: implicit declaration of function `__builtin_isnan' rrdtoolmodule.c:202: warning: nested extern declaration of `__builtin_isnan' rrdtoolmodule.c: In function `PyRRD_info': rrdtoolmodule.c:449: warning: nested extern declaration of `__builtin_isnan' rrdtoolmodule.c:469: warning: nested extern declaration of `__builtin_isnan' *** Error code 1 make: Fatal error: Command failed for target `rrdtoolmodule.o' Current working directory /RRDTool/rrdtool-1.2.19/bindings/python *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \  case $f in \    *=* | --[!k]*);; \    *k*) failcom='fail=yes';; \  esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list=' python'; for subdir in $list; do \  echo "Making $target in $subdir"; \  if test "$subdir" = "."; then \    dot_seen=yes; \    local_target="$target-am"; \  else \    local_target="$target"; \  fi; \  (cd $subdir && make  $local_target) \  || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \  make  "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /RRDTool/rrdtool-1.2.19/bindings *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \  case $f in \    *=* | --[!k]*);; \    *k*) failcom='fail=yes';; \  esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src bindings doc examples'; for subdir in $list; do \  echo "Making $target in $subdir"; \  if test "$subdir" = "."; then \    dot_seen=yes; \    local_target="$target-am"; \  else \    local_target="$target"; \  fi; \  (cd $subdir && make  $local_target) \  || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \  make  "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /RRDTool/rrdtool-1.2.19 *** Error code 1 make: Fatal error: Command failed for target `all' [root at dc1u011 rrdtool-1.2.19]# Kindly provide me the solution. With Regards, Jayanta.

1 0