On Wed, 2017-08-09 at 21:22 +0800, Gris Ge wrote:
> diff --git a/multipathd/cli.c b/multipathd/cli.c
> index 32d49766..002abe61 100644
> --- a/multipathd/cli.c
> +++ b/multipathd/cli.c
> @@ -475,7 +475,7 @@ parse_cmd (char * cmd, char ** reply, int * len, void *
> data, int timeout )
> /*
>
On Wed, Aug 09, 2017 at 03:03:00PM +, Bart Van Assche wrote:
> > diff --git a/multipathd/main.c b/multipathd/main.c
> > index 4be2c579..67997d08 100644
> > --- a/multipathd/main.c
> > +++ b/multipathd/main.c
> > @@ -198,7 +198,7 @@ int set_config_state(enum daemon_status state)
> >
Issue:
When multipathd is starting up, it will reply "timeout\n" immediatly
when got any IPC command from socket. The expected way is to wait
uxsock_timeout/1000 seconds.
Root cause:
pthread_mutex_timedlock() are expecting a CLOCK_REALTIME time.
Fix:
Use CLOCK_REALTIME for
