Activity
From 09/18/2017 to 10/17/2017
10/17/2017
- 11:09 PM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- Thanks a lot!
- 08:34 PM Feature #2740 (Resolved): screens hardcopy function could be used to retrieve a log in case a com...
- Seems to work. Note that screen hardcopy is linewrapped, contains initial newlines, etc. Added trimming and a comment...
10/16/2017
- 12:17 AM Revision 2d66536a (vdemo): bash read timeout exit code is different
- 11:56 PM Revision 9bce4b91 (vdemo): all fifo writes and reads are bash only and reduce blocking.
- 02:34 AM Revision 663ab41c (vdemo): removed tail and cat from the ssh connections, if this is stable more ...
10/15/2017
- 05:33 PM Revision 6c877d71 (vdemo): changed the connection timeout code to bash only. killall ssh does not...
- 02:06 PM Revision 3720591b (vdemo): changed msg
- 02:05 PM Revision 346897c8 (vdemo): improved readability. automatic screen scrollback buffer hardcopy/dump...
- 01:44 PM Revision 07f614c6 (vdemo): improved readability. automatic screen scrollback buffer hardcopy/dump...
10/13/2017
- 01:03 AM Bug #2739 (Resolved): logrotate feature interferes with basic startup / error checking behavior
- 12:48 AM Revision f0c34aa0 (vdemo): helper script to rotate logfiles
- 12:40 AM Revision 86147320 (vdemo): logrotation, changed config to VDEMO_LOG_ROTATION=N
- 08:05 PM Revision 558bbc53 (vdemo): changed LOG_ROTATION to VDEMO_LOG_ROTATION now using yes instead of ON...
10/12/2017
10/05/2017
- 05:48 PM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- OK. Then go for it. Please use the same file name as for logs. Only do the dump, when logging is disabled ;-)
- 05:47 PM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- I see, got it. Yes, I would keep it in any case, since the performance impact should be minimal and there is no risk ...
- 05:32 PM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- > So the screen should close only after cmd is completed (or killed).
My questions is, how you decide whether to k... - 05:12 PM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- Hmm, placing the function after the call to @component@ would catch it. E.g. here before sleep 0.01: source:vdemo_bas...
- 09:11 AM Feature #2740: screens hardcopy function could be used to retrieve a log in case a component cras...
- Looks like an interesting feature. But if the component crashed, the screen would been gone already too, wouldn't it?...
- 02:31 AM Feature #2740 (Resolved): screens hardcopy function could be used to retrieve a log in case a com...
- The following idea came to my mind when investigating how to retrieve screen buffers in a script:
@screen -S "some.s... - 09:13 AM Feature #2682 (Feedback): Periodic check while component is running
- Wasn't there a warning on the command line, that component monitoring will not be available?
- 09:12 AM Bug #2739: logrotate feature interferes with basic startup / error checking behavior
- Go for it.
- 09:11 AM Bug #2741: text-based remote-control of vdemo gui needs improvement
- It would be great, if you could propose a pull request.
- 03:39 AM Bug #2741 (Resolved): text-based remote-control of vdemo gui needs improvement
- The vdemo with the --fifo option uses a fifo and a text file for the responses.
vdemo responds to commands and wri... - 09:07 AM Feature #2681 (Resolved): new release?
- I pushed a new branch 0.6. Anything else to do for a release here?
Sorry for the delay, I didn't received a notifica...
10/04/2017
- 01:59 AM Bug #2739 (Resolved): logrotate feature interferes with basic startup / error checking behavior
- In my view the most basic vdemo behavior is:
# start component
# if the component does not crash within x seconds, ...
Also available in: Atom