Re: thoughts on updates for obj with guarded attribute

["Wilfried Woeber, UniVie/ACOnet" <]

>
>Wilfried, if you still have the example you sent in, please forward it to us
>to see if we can reproduce and fix.

Here we go:
...........................................................................
From:	ACCESS::WOEBER "Wilfried Woeber, UniVie/ACOnet" 30-SEP-1993 17:41:14.06
To:	RIPE-DBM
CC:	MX%"tkjg@localhost",MX%"pkl@localhost",WOEBER
Subj:	update connect: for CESNET-A in database

inetnum:   192.108.151.0
netname:   CESNET-A
descr:     Czech Educational and Scientific network
descr:     Prague
country:   CZ
admin-c:   Jan Gruntorad
tech-c:    Petr Kral
tech-c:    Jiri Orsag
tech-c:    Pavel Vachek
connect:   ACONET RIPE NSF
changed:   ors@localhost 930912
changed:   woeber@localhost 930930
source:    RIPE
........................................................................... 
You see, there was no bdrygw-l: line.
This was the answer:
........................................................................... 
Date: Thu, 30 Sep 1993 17:41:38 +0100
To: "Wilfried Woeber, UniVie/ACOnet" <Wilfried.Woeber@localhost
From: RIPE Database Management ripe-dbm@localhost
Subject: Re: update connect: for CESNET-A in database

Your e-mail:

>   From:    "Wilfried Woeber, UniVie/ACOnet" woeber@localhost
>   Subject: update connect: for CESNET-A in database
>   Date:    Thu, 30 Sep 1993 17:41:12 +0100
>   Msg-Id:  <00973541.749E8040.4828@localhost

has been processed by the automatic update procedure at the RIPE NCC.
Diagnostic output follows:

------------------------------------------------------------------------
inetnum:   192.108.151.0
netname:   CESNET-A
descr:     Czech Educational and Scientific network
descr:     Prague
country:   CZ
admin-c:   Jan Gruntorad
tech-c:    Petr Kral
tech-c:    Jiri Orsag
tech-c:    Pavel Vachek
connect:   ACONET RIPE NSF
bdrygw-l:  ACONET ACONET
changed:   ors@localhost 930912
changed:   woeber@localhost 930930
source:    RIPE
WARNING:   guarded field bdrygw-l reset to current value


Objects that just generated a WARNING have been updated as shown.
[....]
...........................................................................
Right now, reviewing it, I just notice that this was another instance where
I've seen duplicated bdrygw-l: flags. Maybe this can serve as a clue...

>Cheers from Interop,

Have a good time there,
cheers,

Wilfried.