Hi Bahaa,

Al-Amood, Bahaaldin wrote:

I am testing the snap from the 9th of Dec. I noticed that in the
> ca_node.conf file you have put all the commands on one line.
it is good if every thing goes well but if one of them fails, we would not have a way to detect what had happened and where it failed.
I am thinking may be it would be better if these commands where
separated and some error checking is added to it.
I fixed the command in export-import.lib. The export, import, start and
stop options accept lists too. Example:

EXPORT_IMPORT_DOWN_START "start interface" "test interface"

Now we first execute "start interface" and if it doesn't fail then we execute "test interface". I think this is the solution for the described problem.

another thing is it possible to make the ra machine private ip
address a configure option. as of now it is fixed to ra.openca.org?
Sorry, but I don't understand the question. It is no problem to add a new configure option but what do you want to do with this new option?

Best regards

Michael

P.S. for Bahaa: I removed ie_req and spkac_req. They are now integrated into basic_csr (incl. automatic browserdetection). So dc-style is supported for alle parts of the software. We must "only" find a way now to switch between the styles.
--
-------------------------------------------------------------------
Michael Bell Email (private): [EMAIL PROTECTED]
Rechenzentrum - Datacenter Email: [EMAIL PROTECTED]
Humboldt-University of Berlin Tel.: +49 (0)30-2093 2482
Unter den Linden 6 Fax: +49 (0)30-2093 2959
10099 Berlin
Germany http://www.openca.org



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to