For anyone who doesn't remember this thread of a few days ago, I had some log
files whose permissions were being randomly changed to 600 (after I set them
to 644). Ths was happening several times a day.
OK - there's a new application in the Mandrake 9.0 Control Panel called
drakperm. It
On Thu, 26 Dec 2002, shlomo solomon wrote:
For anyone who doesn't remember this thread of a few days ago, I had some log
files whose permissions were being randomly changed to 600 (after I set them
to 644). Ths was happening several times a day.
OK - there's a new application in the Mandrake
On Thursday 26 December 2002 17:44, Tzafrir Cohen wrote:
But how are those permissions set to the files?
Isn't it by a daily cron job (msec)?
Yes, but it's an hourly CRON job on my MDK 9.0 box. And that's apparently the
default - I didn't make any changes to system jobs after installing.
--
On Saturday 21 December 2002 05:32, Xavier Gentoo wrote:
My guess would be that you shouldn't be logging into a separate logfile at
all. See logger(1).
I don't think that's relevant. As I understand it, logger allows writing to
syslog which is not what I want. My script checks if ADSL is up
On Sat, 21 Dec 2002, shlomo solomon wrote:
On Saturday 21 December 2002 05:32, Xavier Gentoo wrote:
My guess would be that you shouldn't be logging into a separate logfile at
all. See logger(1).
I don't think that's relevant. As I understand it, logger allows writing to
syslog which isnot
On Saturday 21 December 2002 21:56, Tzafrir Cohen wrote:
logger is indeed such a quick-and-dirty tool...
I'll try it - but aside from my curiosity about what's causing this, it's not
a high priority item (at least until I finish lots of other things I want to
fix on my system), since as I wrote
On Thu, 19 Dec 2002, Arie Folger wrote:
On Thursday 19 December 2002 11:19, shlomo solomon wrote:
I have a strange problem. Actually, I've solved it, but I don't like the
solution and I don't like not knowing what's causing it. So maybe someone
can help.
snip
The problem is that every
On Thu, 2002-12-19 at 18:19, shlomo solomon wrote:
The problem is that every so often (I don't know when it happens), the
permission becomes 600 and non-root users can no longer read the file. There
are also some gz files in the /var/log/mylogs directory (created by
logrotate). The same
On Thursday 19 December 2002 18:41, Gilad Ben-Yossef wrote:
I bet that logrotate is the one to blame for this. It simply creates the
files with it's default permissions. Check logrotate config file for the
dirty details.
I already thought of that, but eliminated the possibility because this
On Thursday 19 December 2002 11:19, shlomo solomon wrote:
I have a strange problem. Actually, I've solved it, but I don't like the
solution and I don't like not knowing what's causing it. So maybe someone
can help.
snip
The problem is that every so often (I don't know when it happens), the
Hypothesis:
When logrotate rotates away log files, your cron job has to create a new
log file. This new log file apparently gets the default (for root cron
jobs) permission of 600.
A solution: have your cron job change the permission of your log file
each time it writes; or before writing it is
11 matches
Mail list logo
