> I noticed that several savesets that were not cloned all have the same
> cloneid. I understand that every saveset is a clone of itself, and all
> savesets should have unique ssids unless one of them is an "actual"
> clone of the other, but why would different savesets, each having a
> unqiue ssid, have the same cloneids?

Were they all kicked off at the same time?  Most of my cloneids appear
to be identical to 'nsavetime'.

$ mminfo -av -r 'ssid,cloneid,nsavetime'
 ssid         clone id  save time
559752705   1075927189 1075927189
599987201   1076085426 1076085426
[snip]

By using a timestamp of when the clone was created, it should be unique
for a given ssid.

Although I wonder what would happen if you cloned A to B, then kicked
off clones at the same moment for A->C and B->D.  Presumably database
constraints would keep them from getting the same cloneid.

> Seems if two ssids are different then their corresponding cloneids
> should be too?

I see no reason for that.

--
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=