Re: {bb} No email notification Solaris 9 and bb1.9f-btf

[Philip Clark <bblist@cannae.uklinux.net>]

A couple of things occur to me. First, I'd check the setting of MAXLINE
in bb.h to make sure that it's sensible. E.g.:

  #define MAXLINE  8192

Then, I'd stop BB and move my bbwarnrules.cfg out of the way. Then I'd
re-create a new version of the file by hand using "vi" to make sure that
no control characters get included.

If this still does not help, I'd try moving the lines:

#if DEBUG
  debug("dst: [%s] from: [%s] to: [%s] dstmaxlen:
[%d]\n",dst,from,to,dstmaxlen);
#endif

near the top of the "replacestr" procedure in utils.c from out of the
"if" clause, so that you get detailed debug output for all calls and
not just the null string ones. Hopefully, that should provide some
more clues.

Cheers, Phil.



On Sun, 2005-06-26 at 14:41, Al Rankin wrote:
> I was beginning to think that I had problems w/ grep or egrep but after surfing through the source code I realize there is a function written to emulate egrep.  I put utils.c in DEBUG, recompiled and ran bb for a bit and got more information about the strings not matching:
> *---------------------------------------------
> hostsvc: medspeak.msgs
> 2nd word in message is: <yellow>
> color of msg: yellow
> bbwarn: TRUE
> INTO REPLACESTR
> String returned: [yellow red]
> The pagelevels is set to <yellow red>
> pagedelay: 30
> cfgdelim: ;
> svcerrlist: conn:100 ftp:101 telnet:102 http:103 smtp:104 disk:200 cpu:201 procs:300 svcs:301 msgs:302 oracle:400 sql-server:401 dblic:402 dbsz:403 impax:500 offline:501 dicom:502 errpt:600 fax:601 jobs:602 prt:603 who:604 ERR:999
> pagehelpcode: 911
> INTO REPLACESTR
> String returned: [medspeak]
> hostinfo: (hostsvc:medspeak.msgs) (bbhostsvc:medspeak.msgs) (redhost:medspeak) (redsvc:msgs)
> ignforall: 
> machip: 192168016055 - redsvc: msgs - svcerr: 302
> rule line: * ; ; * ; ; * ; 0600-2300 ; pg-nspacs pg-nspacspager
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 1: *
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 2: 
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 3: *
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 4: 
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 5: *
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 6: 0600-2300
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Column 7: pg-nspacs pg-nspacspager
> Substituting hg- tags in the rule line
> Original column 1:       *
> Checking host definition: *
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Included hosts are: <*>
> INTO REPLACESTR
> String returned: [*]
> Column 1 converted to a regex: <*>
> Original column 2:       
> INTO REPLACESTR
> dst: [] from: [  ] to: [ ] dstmaxlen: [0]
> Excluded hosts are: <>
> Trying to match host <medspeak> with hosts regex: *
> INTO REPLACESTR
> String returned: [^(*)$]
> INTO REPLACESTR
> match on [*]
> dsttmp at this point: [^(.*], dst: [)$]
> [*] generates a string too large, stopped !   <----- interesting
> Matching <medspeak> against <^(.*>
> Ignore this rule as host <medspeak> did not match this regex: *
> Oh well, no recipients were determined, we're done
> *-------------------------------------------------------------------------------------
>  
> the lines:
> Trying to match host <medspeak> with hosts regex: *
> INTO REPLACESTR
> String returned: [^(*)$]
> INTO REPLACESTR
> match on [*]
> dsttmp at this point: [^(.*], dst: [)$]
> [*] generates a string too large, stopped !
> 
> are interesting, and maybe there is a memory allocation problem when trying to do the regexp. ???  Anyone got any thoughts ?


-- 
Weinberg's Principle: An expert is a person who avoids the small errors
while sweeping on to the grand fallacy.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.