Logrotate set permis to 0600 (?)
Closed this issue · 6 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. The honssh.log reaches the point where it should be rotated and a new
logfile created
2. When the old log files is moved to honssh.log.1 and a new honssh.log is
created its permissions seems to be set to 0600
What is the expected output?
Expected log file permissions to be 0640 or 0644
What do you see instead?
Log file permissions are set to 0600
What version of the product are you using?
56dfab7e24f1
On what operating system?
OpenBSD 5.3/5.4
Please provide any additional information below.
Original issue reported on code.google.com by are.hans...@gmail.com
on 25 Mar 2014 at 9:12
GoogleCodeExporter commented
The log file rotation is handled by twisted, not sure there's much I can do :(
Original comment by tnn...@googlemail.com
on 25 Mar 2014 at 3:41
GoogleCodeExporter commented
Ouch...
They way it appears is that it's creating new logs with 0600 for the user it's
running as. It's easy to work around it tho.
Did you use a update version of twisted in the latest release of HonSSH?
Original comment by are.hans...@gmail.com
on 25 Mar 2014 at 4:03
GoogleCodeExporter commented
Twisted is installed by the user (normally a package called python-twisted or
similar) - it's not distributed with HonSSH :)
Just looking at my HonSSH setup and the logs are created with 644 and the
permissions remain when rotated as 644 :S
-rw-r--r-- 1 root root 308170 Mar 25 12:07 honssh.log
-rw-r--r-- 1 root root 1000058 Mar 20 10:20 honssh.log.1
-rw-r--r-- 1 root root 1000066 Mar 19 10:35 honssh.log.2
-rw-r--r-- 1 root root 1000026 Mar 18 10:07 honssh.log.3
Original comment by tnn...@googlemail.com
on 25 Mar 2014 at 4:58
GoogleCodeExporter commented
Yepp i caught my self on that 2sec after posting it:P
Hmm...gotta look at what going on with Bifrozt then, strange issue tho. I know
you fixed the permission issue, so it can't be that, can't really figure out
what's causing this.
*adding more grey hairs*
Original comment by are.hans...@gmail.com
on 25 Mar 2014 at 5:04
GoogleCodeExporter commented
Haha, well I'll close the issue because its outside of HonSSH really, but I'm
still interested in solving it for you :P
What permissions does your log folder have? I fixed the permissions for all log
files that HonSSH generates but not honssh.log
Original comment by tnn...@googlemail.com
on 25 Mar 2014 at 5:25
- Changed state: Invalid
GoogleCodeExporter commented
Hehe fair enough.
Cool appreciate it man, I'm at work now tho.
I'll ping you when I get home.
Sent from my Nokia 3310.
Original comment by are.hans...@gmail.com
on 25 Mar 2014 at 5:31