[Xastir] Killed object reborn by xastir

[Gerry Creager n5jxs]

I saw something like this in the past.  Several CVS updates ago... and 
at least one major release in the past.

In my case, it was caused by an improper shutdown of Xastir.  When it 
restarted, it regenerated the object.

gerry

Curt, WE7U wrote:
> On Tue, 25 Jan 2005, Tapio Sokura wrote:
> 
> 
>>About a week ago I created an object and it was live for some hours.
>>Then someone else killed it by sending only one packet. Xastir picked
>>that up and kept resending the kill-packet for a while. No problem here.
>>
>>Today I restarted Xastir and the same object popped back up to the map
>>and I had to kill it again. Has anyone else seen this behavior?
> 
> 
> I have not, but I don't often see a lot of the type of activity you
> describe.
> 
> Xastir records all of the interesting info about its own
> objects/items in the ~/.xastir/config/object.log file.
> 
> If you kill an object the lines corresponding to that object that
> are still live should get a hash mark prepended to them.  Same for
> if someone else takes over or kills your object.  Perhaps one of
> those scenarios didn't get tested fully.
> 
> Please add it to the bug-list, with as much detail as possible so
> that one of us can recreate the problem.
> 
> --
> Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
> "Lotto:    A tax on people who are bad at math." -- unknown
> "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> "The world DOES revolve around me:  I picked the coordinate system!"
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> https://lists.xastir.org/mailman/listinfo/xastir

-- 
Gerry Creager -- gerry.creager at tamu.edu
Texas Mesonet -- AATLT, Texas A&M University	
Cell: 979.229.5301 Office: 979.458.4020
FAX:  979.847.8578 Pager:  979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843