#176 Updating span lsoCmd does not launch new lso process

[Anonymous]

Unsure whether to classify this as a bug as it may be intended behavior, but in my opinion it can lead to confusion.

When calling updateSpan (c span [args] in ltpadmin), if the lsoCommand of span is changed, a new process is not launch for the new lsoCommand. In my opinion, if there is a change in the lsoCommand, the current process running the now defunct lsoCommand should be stopped and a new one should be started. The current behavior is that the defunct lsoCommand process hangs around until the span is restarted manually or by some other means.

[Jay Gao]

We added some documentation on the current behavior, which requires the ltp engine to restart. We may consider enabling individual span to update itself if there is a strong need for this flexibility. For now we will document the behavior as you pointed out.