Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rtcd.log can become gigabyte large #355

Open
130s opened this issue Apr 9, 2015 · 0 comments
Open

rtcd.log can become gigabyte large #355

130s opened this issue Apr 9, 2015 · 0 comments

Comments

@130s
Copy link
Contributor

130s commented Apr 9, 2015

I don't know if this is Hiro/NXO question. I don't know either the condition when this can happen. But I got from a user a single rtcd.log file that is 1.4G. It's content is mostly lines like below. Too large log files like this are difficult to handle in any way. Is there a way to set the maximum size of a single log file?:

position limit over RARM_JOINT2(5), qRef=-2.80412, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle =
 -2.80412
position limit over LARM_JOINT2(11), qRef=-2.79798, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle 
= -2.79798
position limit over RARM_JOINT2(5), qRef=-2.80412, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle =
 -2.80412
position limit over LARM_JOINT2(11), qRef=-2.79798, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle 
= -2.79798
position limit over RARM_JOINT2(5), qRef=-2.80412, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle =
 -2.80412
position limit over LARM_JOINT2(11), qRef=-2.79798, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle 
= -2.79798
position limit over RARM_JOINT2(5), qRef=-2.80412, llimit =-2.75762, ulimit =0, servo_state = ON, prev_angle =
 -2.80412

UPDATE There are open PRs https://github.com/start-jsk/hironx-package/pull/112 and https://github.com/start-jsk/hironx-package/pull/114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant