NOTIFY(SOA) for zone already xferring

Scott Bertilson scott at nts.umn.edu
Wed Feb 28 03:36:45 UTC 2001


Don't think it applies.  Note that I said in my note that zone
state flags were 0x8043.  Z_XFER_RUNNING is 0x4.
					Thanks, Scott
> 
> 1152.   [bug]           ixfr processing could leave Z_XFER_RUNNING set.
> 
> Index: bin/named/ns_maint.c
> ===================================================================
> RCS file: /proj/cvs/isc/bind8/src/bin/named/ns_maint.c,v
> retrieving revision 8.118
> retrieving revision 8.119
> diff -u -r8.118 -r8.119
> --- ns_maint.c	2001/02/04 12:49:37	8.118
> +++ ns_maint.c	2001/02/08 01:27:47	8.119
> @@ -1599,7 +1599,6 @@
>  					break;
>  
>  				case XFER_SUCCESSIXFR:
> -					zp->z_flags |= Z_XFER_RUNNING;
>  					zp->z_xferpid = XFER_ISIXFR;
>  					ns_notice(ns_log_default,
>  						  "IXFR Success %s",
> @@ -1624,8 +1623,6 @@
>  						ns_notice(ns_log_default,
>  							"IXFR Merge failed %s",
>  							  zp->z_ixfr_tmp);
> -					zp->z_flags &=
> -						~(Z_XFER_RUNNING|Z_XFER_ABORTED|Z_XFER_GONE);
>  						ns_retrytime(zp, tt.tv_sec);
>  						sched_zone_maint(zp);
>  					}


More information about the bind-users mailing list