[00:00] <rk[abc]> causing any performance issues?
[15:57] <phutchins> Anyone know how to control the user and group of upstart logs?
[15:58] <phutchins> I.E. I need the group of /var/log/upstart/mylog.log to not be root, or be word readable, even after the file is rotated.
[19:42] <rk[abc]> phutchins: i think your best bet is to create a cronjob that copies the logs and changes permissions on the copy.
[19:42] <rk[abc]> or maybe trying an aggregate logger program like logstash
[20:19] <phutchins> I ended up just logging to file and using logrotate.d where you can specify ownership of the file
[20:19] <phutchins> doesn't seem that upstarts logging function allows any sort of configuration of permisisons or ownership of the logs that it writes
[22:52] <shrabok> is there someone that can help with an issue I am having with upstarts respawning?
[22:54] <shrabok> I have an upstart that runs an ssh tunnel script but it can occasionally fail the first few tries waiting for dns to propagate, but when the script fails the upstart will reach a running state and than respawn
[22:55] <shrabok> I have another upstart that depends on this upstart running before it starts. But the upstart states its reach running state and then respawns and as a result the dependent upstart runs