Re: [Iscsitarget-devel] Beta for online database storage ready (RFC)

[Jeff W. <tru...@gm...>]

On Jul 7, 2008, at 12:49 PM, Arne Redlich wrote:

> Am Freitag, den 04.07.2008, 11:51 -0700 schrieb Jeff Waller:
>> See "Online target database?" thread for info.  Following up from  
>> that
>> thread, I've
>> made the following changes, and require some feedback (see below).
>>
>> ==========================================================
>> 1) Updated ietadm and the ietd<--->ietadm protocol to allow a -- 
>> sync option.
>> If present,
>> this will cause ietd to first perform the changes specified by the  
>> other
>> operator
>> present on the command line for ietadm, and then after those  
>> changes are
>> complete
>> will write our a new configuration file named basename.x where:
>>
>> basename is the name of the configuration file ietd was invoked  
>> with (e.g.
>> /etc/ietd.conf).
>> x is a number extending the filename.
>>
>> So if ietd was started with /etc/ietd.conf, the new configuration  
>> file would
>> be named
>> /etc/ietd.conf.1.
>
> Why? And the next update will generate ietd.conf.2?

Yes.  Each synchronized update generates a new file with the next higher
extension number.

> Why not simply add a --outfile option?

I'm guessing at this question, I think the question is why not augment
ietadm and the protocol to allow for a means of what the output file
should be named.  I'm  opposed to exporting administrative control of
filenames to ietadm.  In other words, IMHO, all ietd should tell ietadm
is "it's stored" and by design avoid revealing any details of how it  
did so.

-Jeff