sessiond: document effect of rotated_after_last_stop on clear

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Change-Id: I81e758aee375f297647bcf9c9a469f867799358a
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

diff --git a/src/bin/lttng-sessiond/session.h b/src/bin/lttng-sessiond/session.h
index 606c42269b4f9b4d4576536c8b113d2493d5fa1e..883a265545e6965e2a82286cbcb6592d9781168c 100644 (file)
--- a/src/bin/lttng-sessiond/session.h
+++ b/src/bin/lttng-sessiond/session.h
@@ -172,7 +172,8 @@ struct ltt_session {
         * Keep a state if this session was rotated after the last stop command.
         * We only allow one rotation after a stop. At destroy, we also need to
         * know if a rotation occurred since the last stop to rename the current
-        * chunk.
+        * chunk. After a stop followed by rotate, all subsequent clear
+        * (without prior start) will succeed, but will be effect-less.
         */
        bool rotated_after_last_stop;
        /*