(2013/10/18 11:19), Steven Rostedt wrote:
On Fri, 13 Sep 2013 11:06:32 +0900
Yoshihiro YUNOMAE wrote:
diff --git a/trace-msg.c b/trace-msg.c
new file mode 100644
index 000..cf82ff6
--- /dev/null
+++ b/trace-msg.c
@@ -0,0 +1,683 @@
+/*
+ * trace-msg.c : define message protocol for communic
On Fri, 13 Sep 2013 11:06:32 +0900
Yoshihiro YUNOMAE wrote:
> diff --git a/trace-msg.c b/trace-msg.c
> new file mode 100644
> index 000..cf82ff6
> --- /dev/null
> +++ b/trace-msg.c
> @@ -0,0 +1,683 @@
> +/*
> + * trace-msg.c : define message protocol for communication between clients
> and
On Thu, 17 Oct 2013 15:34:17 +0900
Yoshihiro YUNOMAE wrote:
>recorder error in splice output
>
> It seems to be not due to applying my patch.
> We cannot use "localhost" for trace-cmd(v1.2).
> When we use "127.0.0.1", this problem does not occur.
You're right. Hmm, it's actually quite annoyi
(2013/10/15 11:21), Steven Rostedt wrote:
On Fri, 13 Sep 2013 11:06:32 +0900
Yoshihiro YUNOMAE wrote:
Apply trace-msg protocol for communication between a server and clients.
Currently, trace-listen(server) and trace-record -N(client) operate as follows:
listen
On Fri, 13 Sep 2013 11:06:32 +0900
Yoshihiro YUNOMAE wrote:
> Apply trace-msg protocol for communication between a server and clients.
>
> Currently, trace-listen(server) and trace-record -N(client) operate as
> follows:
>
>
> listen to socket fd
>
Apply trace-msg protocol for communication between a server and clients.
Currently, trace-listen(server) and trace-record -N(client) operate as follows:
listen to socket fd
connect to socket fd
accept the client
send "tracecmd
6 matches
Mail list logo