Matthew Richardson wrote:
> Mike Christie wrote:
>> What are you trying to accomplish? The manual add threw me.
>> Normally when you do
>> iscsiadm -m discovery -t st -p .....
>> it will create some files in /etc/iscsi/nodes (or /var/lib/iscsi/nodes 
>> in some distros). Then you can set the node.startup value to control if 
>> when the iscsi service is started if you want the tools to automatically 
>> log in for you.
>> With the
>> iscsiadm -m node -T .. -p .. -o new
>> it creates some files in the nodes dir and you can again set if you want 
>> the tools to autologin or not.
>> For the second option you listed (the manual add one), it seems like if 
>> you were going to write out a list of portal,target,iface tuples that 
>> you want to log into, then it is same as doing iscsiadm -o new command 
>> (iscsiadm -o new would be writing the file for you basically). Are you 
>> just trying to not have to run iscsiadm at all?
> At the moment I'd have to either put a startup script in place, or
> manually run the above commands at least once to get targets etc added
> to the iscsi database.
> I'd like to be able to deliver a config file to the system, and have the
> system do the creation of ifaces, and the discovery (or manual add) or
> targets as part of its startup (e.g in the init.d script), as well as

When we parse the cofig file and make ifaces and do discovery or 
manually add, do you want us to also add the info the iscsi DB or just 
use that info to create sessions while the iscsi service is running that 
one time?

> the 'loginall' it currently does.  A config file listing ifaces,
> portals, targets etc seemed to be the right way to do this - it being
> parsed by a startup script.
> Hope this makes sense.
> Thanks,
> Matthew

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to