Re: [Freeipmi-devel] kcs library with synchronization

[Albert Chu]

Oh, I forgot, also ...

ipmi_kcs_cmd_timeout(port, req_data, req_data_len, res_data,
res_data_len, struct timeval *t);

Same as ipmi_kcs_cmd, but times out after the time.  I think this
function is essential, b/c we don't know how long anyone may hold the lock.

Al

--
Albert Chu
address@hidden
Lawrence Livermore National Laboratory

----- Original Message -----
From: Albert Chu <address@hidden>
Date: Friday, March 19, 2004 8:39 am
Subject: [Freeipmi-devel] kcs library with synchronization

> Hey everyone,
> 
> I thought about it a bit, and I think the following may be best for 
> theKCS library to handle our sync issue.
> 
> ipmi_kcs_cmd(port, req_data, req_data_len, res_data, res_data_len);
> ipmi_kcs_clean_locks();
> ipmi_kcs_setup_cleanup_signal_handler(signum);
> ipmi_kcs_setup_default_cleanup_signal_handlers();
> 
> ipmi_kcs_cmd - handles the read and write, handles the sync stuff.
> 
> ipmi_kcs_clean_locks - unlocks any locks current process has.  
> Primarilyfor users to implement within their signal handlers.
> 
> ipmi_kcs_setup_cleanup_signal_handler - let libfreeipmi setup the
> cleanup signal handler for the user instead.  The signal handler just
> calls ipmi_kcs_clean_locks.
> 
> ipmi_kcs_setup_default_cleanup_signal_handlers - calls
> ipmi_kcs_setuP_cleanup_signal_handler for the most common signals.
> 
> Al
> 
> --
> Albert Chu
> address@hidden
> Lawrence Livermore National Laboratory
> 
> 
> 
> _______________________________________________
> Freeipmi-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/freeipmi-devel
>