> >>> How is this messing you up? This should not affect any of your other
> >>> channels. The only effect is that the sought rules don't get updated.
> >>
> >> I'm not sure how everyone else is doing it, but my script checks for
> >> updates using --channelfile, then runs sa-compile if sa-update returns
> >> 0. If a channel fails, sa-update returns something other than 0. Sure,
> >> my old rules are intact and the server continues to run normally, but
> >> I'm not getting the benefit of updates in other channels.
> >
> > This sounds like an improvement to sa-compile would be beneficial,
> > so as to distinguish 'some updates available' from 'none' and
> > 'all ok, updated'. Please open a feature request.
s/compile/update/ # :)
> In order to properly open a feature request, I'd like to get a better
> idea where you're going with this. It seems to me that a new exit code
> from sa-update would be more appropriate than running sa-compile every
> time just in case. Maybe I misunderstand?
Yup, seems that is it. There are only all-or-nothing exit codes (0 and 4
respectively) in this scenario.
However, not even close to "royally screwing update", as per some
earlier comment.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
