04-24-2002
That is a good workaround. However, I would set it to fire off every 5 minutes.
1,6,11,16,21, etc... * * * * chmod 660 logfile
One other thing, in HPUX in the CDE or TUI (text user interface) we can manage logfiles. Maybe you have a tool that manages logfiles from an OS perspective, like where they are, permissions etc ...
Do you have anything like this?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
there is a directory eg. /home/edp/ , all the files under this directory :
1. the file and directory owner is "user1" ,
2. the permission is 644
I want everyone hv permission to overwrite all files and write a new file to it , but I want the file owner and permssion keep unchange , could... (1 Reply)
Discussion started by: ust
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
When I listed one directory in Sun, it showed that :
-rwsr-xr-x 1 root bsmbin 78004 Oct 21 2004 bsmprsm
I don't know meaning of the character "s" in "rws" above. I have searched in Sun admin documents but no result. Would you please explain it ? :)
Thank you so much. (1 Reply)
Discussion started by: msg098
1 Replies
3. Cybersecurity
Hello,
i need some help/advice on how to solve a particular problem.
these are the users:
|name | group |
---------- ---------------
|boss | department1 |
|assistant | department1 |
|employee | department1 |
|spy | department2 |
this is the... (0 Replies)
Discussion started by: elzalem
0 Replies
4. UNIX for Dummies Questions & Answers
i have two user named sourav and jishu.
i have created a file named source.txt in sourav.
i made another user called shovon.
i want to give read write permission of souce.txt for shovon but not for jishu.
how can i set permission only for jishu ? (1 Reply)
Discussion started by: sourav_ray
1 Replies
5. Solaris
I can't get the exact error message because I am at home, but on Solaris 10u5 machine I have at work, a few services are stuck in the maintenance state with the following error message in the individual service logs (/var/svc/log/FMRI:instance.log):
Cannot chdir: permission denied
Fortunately... (2 Replies)
Discussion started by: ilikecows
2 Replies
6. Solaris
hi frnds
can u explain
/etc/shadow file have read and write permissions for root only
but while normal user changes his passwd it also updated in that file whats the logic behind that. (2 Replies)
Discussion started by: sravan ega
2 Replies
7. Shell Programming and Scripting
Hi All,
https://www.unix.com/unix-advanced-expert-users/105758-chmod-parent-sub-directories.html
I have to change permission for the directories and subdirectories in single command
when googled i found some updates but i understand what is switch.
If there is a command please... (2 Replies)
Discussion started by: thelakbe
2 Replies
8. Emergency UNIX and Linux Support
Hello All, On my SuSE system, I have wtmp log this log file permission is 644 but every reboot the file permission rollback to 664. In the logrotate.conf and logrotate.d/wtmp files the wtmp logrotate set to 644. I would like to know, which "file" or "script" modify the wtmp log to rollback to... (7 Replies)
Discussion started by: kalaso
7 Replies
9. AIX
I'm trying to set the permission for the syslog log file in syslog,conf.
---------
The below is my configuration file
## example:
# "mail messages, at debug or higher, go to Log file. File must exist."
# "all facilities, at debug and higher, go to console"
# "all facilities, at crit or... (1 Reply)
Discussion started by: novaothers
1 Replies
10. UNIX for Dummies Questions & Answers
Only kernel can write to a directory file. Then what does write permission for a directory imply? (2 Replies)
Discussion started by: vijaysy
2 Replies
SAVELOG(8) System Manager's Manual SAVELOG(8)
NAME
savelog - save a log file
SYNOPSIS
savelog [-m mode] [-u user] [-g group] [-t] [-p] [-c cycle] [-l] [-j] [-J] [-1 .. -9] [-C] [-d] [-l] [-r rolldir] [-n] [-q] [-D dateformat]
file ...
DESCRIPTION
The savelog command saves and optionally compresses old copies of files. Older versions of file are named:
file.<number><compress_suffix>
where <number> is the version number, 0 being the newest. Version numbers > 0 are compressed unless -l prevents it. Version number 0 is
not compressed because a process might still have file opened for I/O. Only cycle versions of the file are kept.
If the file does not exist and -t was given, it will be created.
For files that do exist and have lengths greater than zero, the following actions are performed:
1) Version numbered files are cycled. Version file.2 is moved to version file.3, version file.1 is moved to version file.2, and so on.
Finally version file.0 is moved to version file.1, and version file is deleted. Both compressed names and uncompressed names are
cycled, regardless of -l. Missing version files are ignored.
2) The new file.1 is compressed unless the -l flag was given. It is changed subject to the -m, -u, and -g flags.
3) The main file is moved to file.0.
4) If the -m, -u, -g, -t, or -p flags are given, then an empty file is created subject to the given flags. With the -p flag, the file
is created with the same owner, group, and permissions as before.
5) The new file.0 is changed subject to the -m, -u, and -g flags.
OPTIONS
-m mode
chmod the log files to mode, implies -t
-u user
chown log files to user, implies -t
-g group
chgrp log files to group, implies -t
-c cycle
Save cycle versions of the logfile (default: 7). The cycle count must be at least 2.
-t touch new logfile into existence
-l don't compress any log files (default: do compress)
-p preserve owner, group, and permissions of logfile
-j compress with bzip2 instead of gzip
-J compress with xz instead of gzip
For xz no strength option is set, and xz decides on the default based on the total amount of physical RAM. Note that xz can use a
very large amount of memory for the higher compression levels.
-1 .. -9
compression strength or memory usage (default: 9, except for xz)
-C force cleanup of cycled logfiles
-d use standard date for rolling
-D dateformat
override date format, in the syntax understood by the date(1) command
-r use rolldir instead of . to roll files
-n do not rotate empty files
-q be quiet
BUGS
If a process is still writing to file.0, and savelog moves it to file.1 and compresses it, data could be lost.
SEE ALSO
logrotate(8)
Debian 30 Dec 2017 SAVELOG(8)