Xymon Mailing List Archive search

4.2 and Patches question

18 messages in this thread

list Rob Munsch · Wed, 20 Sep 2006 16:09:25 -0400 ·
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).

I'd thought i'd seen some list traffic about an rc2, rc3, etc., with
some (all?) of these patches applied, but i can't seem to find it.

Thanks!

- --
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFEZ/1BvBcJFK6xYURAi5KAJ9VV2xMO9JkMQlSCClny3fvs8m8NwCdFyTT
+s3DWQ0dMirpl6L9mcXd5mA=
=rPeJ
-----END PGP SIGNATURE-----
list Henrik Størner · Wed, 20 Sep 2006 22:16:26 +0200 ·
quoted from Rob Munsch
On Wed, Sep 20, 2006 at 04:09:25PM -0400, Rob Munsch wrote:
Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):

downtime-singlestatus-docs.patch
client-testmode.patch
double-contenttype.patch
client-options.patch
hobbitfetch-dynaddr.patch
infopage-duplicates.patch
solaris-lofs-exclude.patch
web-cookiehandling.patch
osx-host_t.patch
zoomgraph-bgcolor.patch
confreport-critsystems.patch
top-solarisclient.patch
infopage-dynaddr.patch
hobbitd_alert-memleak.patch
httprelay-status.patch
nkview-purple.patch
client-strtok_r.patch
ncv-ignoretext.patch
quoted from Rob Munsch

I'd thought i'd seen some list traffic about an rc2, rc3, etc., with
some (all?) of these patches applied, but i can't seem to find it.
Those were for the Release Candidate (RC) versions that came out before 
the final 4.2.0 release.


Regards,
Henrik
list Charles Jones · Wed, 20 Sep 2006 13:21:29 -0700 ·
Am I correct in that if we grab the latest snapshot that it includes all 
of those patches (and perhaps other unknown stuff)?

-Charles
quoted from Henrik Størner

Henrik Stoerner wrote:
On Wed, Sep 20, 2006 at 04:09:25PM -0400, Rob Munsch wrote:
  
Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).
    
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):

downtime-singlestatus-docs.patch
client-testmode.patch
double-contenttype.patch
client-options.patch
hobbitfetch-dynaddr.patch
infopage-duplicates.patch
solaris-lofs-exclude.patch
web-cookiehandling.patch
osx-host_t.patch
zoomgraph-bgcolor.patch
confreport-critsystems.patch
top-solarisclient.patch
infopage-dynaddr.patch
hobbitd_alert-memleak.patch
httprelay-status.patch
nkview-purple.patch
client-strtok_r.patch
ncv-ignoretext.patch

I'd thought i'd seen some list traffic about an rc2, rc3, etc., with
some (all?) of these patches applied, but i can't seem to find it.
    
Those were for the Release Candidate (RC) versions that came out before 
the final 4.2.0 release.
list Bob Gordon · Wed, 20 Sep 2006 13:25:58 -0700 ·
quoted from Charles Jones
On 9/20/06, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):
Any chance of getting a cluster patch (like what was done for the RC's?)

-- 
--==[ Bob Gordon ]==--
list Rob Munsch · Wed, 20 Sep 2006 16:30:42 -0400 ·
quoted from Charles Jones
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Henrik Stoerner wrote:
On Wed, Sep 20, 2006 at 04:09:25PM -0400, Rob Munsch wrote:
Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):

downtime-singlestatus-docs.patch
..8<..

eep!  thanks for the heads-up there.

I can't help but notice that this patch appears last on the patches
page.  Maybe a simple text warning to check the order of the files would
be good there?  I went down the list on /patches top to bottom and got
some strange errors, before it occurred to me to check the actual
chronology.
quoted from Rob Munsch


- --
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFEaTyBvBcJFK6xYURAh6ZAJwKLPzGG9Q0VNoonz4wY7R/TTA4OwCaA547
jZfWTvCaRmroIDLCh09iy1U=
=/o4b
-----END PGP SIGNATURE-----
list Henrik Størner · Wed, 20 Sep 2006 22:35:59 +0200 ·
quoted from Charles Jones
On Wed, Sep 20, 2006 at 01:21:29PM -0700, Charles Jones wrote:
Am I correct in that if we grab the latest snapshot that it includes all 
of those patches (and perhaps other unknown stuff)?
The latest snapshot has these patches included, but also other stuff
that is work-in-progress. And in fact, the snapshots won't compile at
all right now.


Regards,
Henrik
list Nicolas Dorfsman · Thu, 21 Sep 2006 15:28:13 +0200 ·
quoted from Rob Munsch
Le 20 sept. 06 à 22:16, Henrik Stoerner a écrit :
On Wed, Sep 20, 2006 at 04:09:25PM -0400, Rob Munsch wrote:
Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):

downtime-singlestatus-docs.patch
client-testmode.patch
double-contenttype.patch
client-options.patch
hobbitfetch-dynaddr.patch
infopage-duplicates.patch
solaris-lofs-exclude.patch
web-cookiehandling.patch
osx-host_t.patch
zoomgraph-bgcolor.patch
confreport-critsystems.patch
top-solarisclient.patch
infopage-dynaddr.patch
hobbitd_alert-memleak.patch
httprelay-status.patch
nkview-purple.patch
client-strtok_r.patch
ncv-ignoretext.patch

I did use this list.  Bad result :

# for f in `cat ../hop/list`; do gpatch -p0 < ../hop/$f; done
patching file common/bb-hosts.5
patching file hobbitd/hobbitd_client.c
patching file lib/headfoot.c
patching file web/bb-datepage.c
patching file web/bb-eventlog.c
patching file web/bb-findhost.c
patching file web/bb-rep.c
patching file web/bb-snapshot.c
patching file web/hobbit-enadis.c
patching file web/hobbit-nkedit.c
patching file client/runclient.sh
patching file hobbitd/hobbitfetch.c
patching file web/hobbitsvc-info.c
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit- confreport.c.rej
patching file client/hobbitclient-sunos.sh
patching file ./lib/cgi.c
patching file ./lib/cgi.h
patching file ./web/bb-ack.c
patching file ./web/bb-datepage.c
patching file ./web/hobbit-confreport.c
patching file ./web/hobbit-enadis.c
patching file ./web/hobbit-hostgraphs.c
patching file ./web/hobbit-statusreport.c
patching file bbdisplay/bbgen.h
patching file lib/hobbitrrd.c
patching file lib/hobbitrrd.h
patching file lib/htmllog.c
patching file web/hobbitgraph.c
patching file web/hobbitsvc-trends.c
patching file hobbitd/webfiles/zoom.js
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 8.
1 out of 12 hunks FAILED -- saving rejects to file web/hobbit- confreport.c.rej
patching file web/hobbit-confreport.cgi.1
patching file hobbitd/webfiles/confreport_front
patching file web/Makefile
patching file hobbitd/wwwfiles/menu/menu_items.js.DIST
patching file web/hobbit-confreport-critical.sh.DIST
patching file build/bb-commands.sh
patching file client/hobbitclient-sunos.sh
patching file web/hobbitsvc-info.c
patching file hobbitd/hobbitd_alert.c
patching file hobbitd/do_alert.c
patching file lib/cgi.c
patching file hobbitd/webfiles/hobbitnk_footer
patching file web/hobbit-nkview.c
patching file lib/Makefile
patching file lib/color.c
patching file lib/timefunc.c
patching file hobbitd/rrd/do_ncv.c


....and can't compile :

cc -g -O -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 - DSunOS -I. -I/export/home/bigb/hobbit-4.2.0/include -I/usr/local/ include -c -o hobbit-confreport.o hobbit-confreport.c
"hobbit-confreport.c", line 271: warning: assignment type mismatch:
         pointer to char "=" pointer to unsigned char
"hobbit-confreport.c", line 473: warning: assignment type mismatch:
         pointer to unsigned char "=" pointer to char
"hobbit-confreport.c", line 683: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 684: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 685: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 695: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 696: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 697: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 704: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 705: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 706: left operand must be modifiable  lvalue: op "="
"hobbit-confreport.c", line 831: cannot recover from previous errors
cc: acomp failed for hobbit-confreport.c
make[1]: *** [hobbit-confreport.o] Error 2
make[1]: Leaving directory `/export/home/bigb/hobbit-4.2.0/web'
make: *** [web-build] Error 2
list Ralph Mitchell · Thu, 21 Sep 2006 11:18:45 -0500 ·
quoted from Nicolas Dorfsman
On 9/21/06, Nicolas Dorfsman <user-0b8cdfcc881d@xymon.invalid> wrote:
I did use this list.  Bad result :
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
I got the same, but I was applying only one patch at a time, so I was
able to eyeball the reject file, web/hobbit-confreport.c.rej, and make
manual updates.  In your case, the second patch failure probably
overwrote the first reject file, but you may still be able to correct
it because both failures happen around line 600 of
hobbit-confreport.c, if I recall correctly.

Anyway, after manual corrections, the compile worked just fine.

Ralph Mitchell
list Rob Munsch · Thu, 21 Sep 2006 15:23:10 -0400 ·
quoted from Ralph Mitchell
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralph Mitchell wrote:
On 9/21/06, Nicolas Dorfsman <user-0b8cdfcc881d@xymon.invalid> wrote:
I did use this list.  Bad result :
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
Identical results for me.
quoted from Ralph Mitchell
I got the same, but I was applying only one patch at a time, so I was
able to eyeball the reject file, web/hobbit-confreport.c.rej, and make
manual updates.  In your case, the second patch failure probably
I did a batch like Nick.  My (second) .rej has only:

- -----
# cat web/hobbit-confreport.c.rej
***************
*** 8,14 ****
  /*
        */

/*----------------------------------------------------------------------------*/

- - static char rcsid[] = "$Id: hobbit-confreport.c,v 1.17 2006/08/14
20:46:24 henrik Exp henrik $";

  #include <sys/types.h>
  #include <sys/stat.h>
- --- 8,14 ----
  /*
        */

/*----------------------------------------------------------------------------*/

+ static char rcsid[] = "$Id: hobbit-confreport.c,v 1.18 2006/08/18
20:37:26 henrik Exp henrik $";

  #include <sys/types.h>
  #include <sys/stat.h>
- -----

So i can see why this fails; the hobbit-confreport.c i have, even after
the patch batch, is 1.15!
quoted from Ralph Mitchell

overwrote the first reject file, but you may still be able to correct
it because both failures happen around line 600 of
hobbit-confreport.c, if I recall correctly.

Anyway, after manual corrections, the compile worked just fine.
Since this seems consistent, mind hinting at what the first failure was?
  The second seems to be just... the version line... expecting to change
1.17 to 1.18, it finds 1.15.  Okay.  But what's the line ~600 correction..?

I went over the .patches and the web/ files manually, and i can't find
what's missing.  Configure runs, make bombs:

- -----
gcc -g -O2 -Wall -Wno-unused -D_REENTRANT -D_LARGEFILE_SOURCE
- -D_FILE_OFFSET_BITS=64 -DLINUX -I. -I/home/rmunsch/hobbit-4.2.0/include
- -I/usr/include -c -o hobbit-confreport.o hobbit-confreport.c
hobbit-confreport.c: In function 'print_host':
hobbit-confreport.c:271: warning: pointer targets in assignment differ
in signedness
hobbit-confreport.c:473: warning: pointer targets in assignment differ
in signedness
hobbit-confreport.c: In function 'main':
hobbit-confreport.c:683: error: incompatible types in assignment
hobbit-confreport.c:684: error: incompatible types in assignment
hobbit-confreport.c:685: error: incompatible types in assignment
hobbit-confreport.c:695: error: incompatible types in assignment
hobbit-confreport.c:696: error: incompatible types in assignment
hobbit-confreport.c:697: error: incompatible types in assignment
hobbit-confreport.c:704: error: incompatible types in assignment
hobbit-confreport.c:705: error: incompatible types in assignment
hobbit-confreport.c:706: error: incompatible types in assignment
make[1]: *** [hobbit-confreport.o] Error 1
make[1]: Leaving directory `/home/rmunsch/hobbit-4.2.0/web'
make: *** [web-build] Error 2
quoted from Rob Munsch
- -----


- --
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFEuadBvBcJFK6xYURAr+WAJ93yXc9m5DimahCcIxYZhWuM2FkUgCfXlRU
G1kzKqWgrqWvFg7a2Z6wtnY=
=Q0k0
-----END PGP SIGNATURE-----
list Collin McCreath · Thu, 21 Sep 2006 16:28:59 -0400 ·
How do I link my Apache Web Server to use hobbit.  What page to I reference
and what is the syntax ?

Collin
quoted from Ralph Mitchell


On 9/21/06, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid> wrote:
On 9/21/06, Nicolas Dorfsman <user-0b8cdfcc881d@xymon.invalid> wrote:
I did use this list.  Bad result :
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
I got the same, but I was applying only one patch at a time, so I was
able to eyeball the reject file, web/hobbit-confreport.c.rej, and make
manual updates.  In your case, the second patch failure probably
overwrote the first reject file, but you may still be able to correct
it because both failures happen around line 600 of
hobbit-confreport.c, if I recall correctly.

Anyway, after manual corrections, the compile worked just fine.

Ralph Mitchell

list Ralph Mitchell · Thu, 21 Sep 2006 21:02:58 -0500 ·
quoted from Rob Munsch
On 9/21/06, Rob Munsch <user-f39e4aae1456@xymon.invalid> wrote:
I did use this list.  Bad result :

patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
That was the infopage-duplicates.patch.  I just ran it again and the
.rej files looks like this:

web/hobbit-confreport.c.rej
***************
*** 600,606 ****
        int argi, hosti, testi;
        char *pagepattern = NULL, *hostpattern = NULL;
        char *envarea = NULL, *cookie = NULL, *nexthost;
-       char hobbitcmd[1024], procscmd[1024], svcscmd[1024];
          int alertcolors, alertinterval;
        char configfn[PATH_MAX];
        char *respbuf = NULL, *procsbuf = NULL, *svcsbuf = NULL;
--- 600,606 ----
        int argi, hosti, testi;
        char *pagepattern = NULL, *hostpattern = NULL;
        char *envarea = NULL, *cookie = NULL, *nexthost;
+       char *hobbitcmd, *procscmd, *svcscmd;
          int alertcolors, alertinterval;
        char configfn[PATH_MAX];
        char *respbuf = NULL, *procsbuf = NULL, *svcsbuf = NULL;

If you fix up that one line, I think it'll all be good.

Ralph Mitchell
list Jerry Yu · Thu, 21 Sep 2006 23:09:31 -0400 ·
the source tar ball or pre-compiled packages (rpm/deb/etc.) should have an "
apache-hobbit.conf". You can use 'include' directive in Apache's httpd.conf,
or copy+paste the content  to httpd.conf. restart apache.

You can then access the web front of Hobbit at
http://hobbitServer/hobbit/bb.html
quoted from Collin McCreath


On 9/21/06, Collin McCreath <user-39cbd37f3484@xymon.invalid> wrote:
How do I link my Apache Web Server to use hobbit.  What page to I
reference and what is the syntax ?

Collin


On 9/21/06, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid> wrote:
On 9/21/06, Nicolas Dorfsman <user-0b8cdfcc881d@xymon.invalid> wrote:
I did use this list.  Bad result :
patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
I got the same, but I was applying only one patch at a time, so I was
able to eyeball the reject file, web/hobbit-confreport.c.rej, and make
manual updates.  In your case, the second patch failure probably
overwrote the first reject file, but you may still be able to correct
it because both failures happen around line 600 of
hobbit-confreport.c, if I recall correctly.

Anyway, after manual corrections, the compile worked just fine.

Ralph Mitchell

list Rob Munsch · Fri, 22 Sep 2006 15:17:50 -0400 ·
quoted from Ralph Mitchell
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralph Mitchell wrote:
On 9/21/06, Rob Munsch <user-f39e4aae1456@xymon.invalid> wrote:
I did use this list.  Bad result :

patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
That was the infopage-duplicates.patch.  I just ran it again and the
.rej files looks like this:

web/hobbit-confreport.c.rej
***************
*** 600,606 ****
       int argi, hosti, testi;
       char *pagepattern = NULL, *hostpattern = NULL;
       char *envarea = NULL, *cookie = NULL, *nexthost;
-       char hobbitcmd[1024], procscmd[1024], svcscmd[1024];
--- 600,606 ----
       int argi, hosti, testi;
       char *pagepattern = NULL, *hostpattern = NULL;
       char *envarea = NULL, *cookie = NULL, *nexthost;
+       char *hobbitcmd, *procscmd, *svcscmd;
If you fix up that one line, I think it'll all be good.
Yep, tho by the time all the patches got done, this was found ~line
680something or so.  Manually changing that line makes make happier.
quoted from Rob Munsch

Thanks!

- --
Rob Munsch
Solutions For Progress IT
www.solutionsforprogress.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFFDbeBvBcJFK6xYURAj5NAJ4nuCOGyXeNBl6+0fDGDVIsKnvXeQCeILEG
+Z68qjgPQeqf6m5GA7fe/Bo=
=r/Qf
-----END PGP SIGNATURE-----
list Thomas Pedersen · Mon, 25 Sep 2006 13:42:11 +0200 ·
A chanche anybody would make a big patch of all the small ones ?

Are any of the patches related to the client ?

/Thomas
quoted from Ralph Mitchell

Ralph Mitchell wrote:
On 9/21/06, Rob Munsch <user-f39e4aae1456@xymon.invalid> wrote:
I did use this list.  Bad result :

patching file web/hobbit-confreport.c
Hunk #1 FAILED at 600.
Hunk #2 succeeded at 649 (offset 12 lines).
1 out of 2 hunks FAILED -- saving rejects to file web/hobbit-
confreport.c.rej
That was the infopage-duplicates.patch.  I just ran it again and the
.rej files looks like this:

web/hobbit-confreport.c.rej
***************
*** 600,606 ****
       int argi, hosti, testi;
       char *pagepattern = NULL, *hostpattern = NULL;
       char *envarea = NULL, *cookie = NULL, *nexthost;
-       char hobbitcmd[1024], procscmd[1024], svcscmd[1024];
         int alertcolors, alertinterval;
       char configfn[PATH_MAX];
       char *respbuf = NULL, *procsbuf = NULL, *svcsbuf = NULL;
--- 600,606 ----
       int argi, hosti, testi;
       char *pagepattern = NULL, *hostpattern = NULL;
       char *envarea = NULL, *cookie = NULL, *nexthost;
+       char *hobbitcmd, *procscmd, *svcscmd;
         int alertcolors, alertinterval;
       char configfn[PATH_MAX];
       char *respbuf = NULL, *procsbuf = NULL, *svcsbuf = NULL;

If you fix up that one line, I think it'll all be good.

Ralph Mitchell

list Peter Welter · Fri, 29 Sep 2006 14:17:23 +0200 ·
Hi Henryk,

I count 18 patches in your list and I'm missing nkview-purple.patch?!
There are only 17 pages on the patch page.

Am I missing something?

Regards,
Peter


2006/9/20, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid>:
quoted from Rob Munsch
On Wed, Sep 20, 2006 at 04:09:25PM -0400, Rob Munsch wrote:
Am i correct in assuming that the various patches found at
http://www.hswn.dk/hobbitsw/patches/
need to be applied to the current 4.2 tarball up for download?  I'm
going by the timestamps on the files :).
Yes. And it's a good idea to apply them in the sequence of the
timestamsp, i.e. (from first to last):

downtime-singlestatus-docs.patch
client-testmode.patch
double-contenttype.patch
client-options.patch
hobbitfetch-dynaddr.patch
infopage-duplicates.patch
solaris-lofs-exclude.patch
web-cookiehandling.patch
osx-host_t.patch
zoomgraph-bgcolor.patch
confreport-critsystems.patch
top-solarisclient.patch
infopage-dynaddr.patch
hobbitd_alert-memleak.patch
httprelay-status.patch

nkview-purple.patch  <--- this one can not be found?!
client-strtok_r.patch
ncv-ignoretext.patch

list Ryan Jay B. Lapuz · Thu, 27 Sep 2007 10:49:47 +0800 ·
Hi guys,

I tried to add the all in one patch for hobbit 4.2.0 and it run smoothly when I issued the command
[root at hobbit hobbit-4.2.0]# patch -p0 <allinone.patch

So my next step would to re-configure, re-make and re-makeinstall, is this right?

Is my old configuration would be safe without backup if I'll do the next step?

Thanks in advance!

Regards,
Ryan
list Sigurður Guðbrandsson · Thu, 27 Sep 2007 09:05:07 -0000 ·
Hi.

It all really depends on your system. If you are only going to make and make install instead of making a .deb or .rpm package, I would recommend backing up all your data before you go for it. (/usr/lib/hobbit/* and /var/lib/hobbit/*)

It just is the safe bet to do a regular back up of your data, because you never know when you'll have a failure on your hands :)

With regards,
 Sigurður Guðbrandsson
quoted from Ryan Jay B. Lapuz


-----Original Message-----
From: Ryan Jay B. Lapuz [mailto:user-945139049f37@xymon.invalid]
Sent: Thu 9/27/2007 2:49 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] 4.2 and Patches question
 Hi guys,

I tried to add the all in one patch for hobbit 4.2.0 and it run smoothly when I issued the command
[root at hobbit hobbit-4.2.0]# patch -p0 <allinone.patch

So my next step would to re-configure, re-make and re-makeinstall, is this right?

Is my old configuration would be safe without backup if I'll do the next step?

Thanks in advance!

Regards,
Ryan
list Ryan Jay B. Lapuz · Thu, 27 Sep 2007 19:56:13 +0800 ·
Hi!

I already run configure, make, and make install for the all-in-one patch
then I got this error message:

bbgen CRITICAL (RED)
red - Program crashed
Fatal signal caught!

summary of activity
1. patch command - ok
2. ./configure - ok
3. make - with warning but still recommend to run make install
4. make install - ok

page.log:
2007-09-27 19:36:36 Tried to down BOARDBUSY: Invalid argument
2007-09-27 19:36:36 Worker process died with exit code 0, terminating
What seems to be wrong?

Thanks and regards!
Ryan
quoted from Sigurður Guðbrandsson

----- Original Message ----- 
From: "Sigurður Guðbrandsson" <user-f6f2e0690a1f@xymon.invalid>
To: <user-ae9b8668bcde@xymon.invalid>
Sent: Thursday, September 27, 2007 5:05 PM
Subject: RE: [hobbit] 4.2 and Patches question


Hi.

It all really depends on your system. If you are only going to make and make install instead of making a .deb or .rpm package, I would recommend backing up all your data before you go for it. (/usr/lib/hobbit/* and /var/lib/hobbit/*)

It just is the safe bet to do a regular back up of your data, because you never know when you'll have a failure on your hands :)

With regards,
 Sigurður Guðbrandsson


-----Original Message-----
From: Ryan Jay B. Lapuz [mailto:user-945139049f37@xymon.invalid]
Sent: Thu 9/27/2007 2:49 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] 4.2 and Patches question
 
Hi guys,

I tried to add the all in one patch for hobbit 4.2.0 and it run smoothly 
when I issued the command
[root at hobbit hobbit-4.2.0]# patch -p0 <allinone.patch

So my next step would to re-configure, re-make and re-makeinstall, is this 
right?

Is my old configuration would be safe without backup if I'll do the next 
step?

Thanks in advance!

Regards,
Ryan