Syslogs permission not getting changed - aix 6.1 | Unix Linux Forums | AIX

  Go Back    


AIX AIX is IBM's industry-leading UNIX operating system that meets the demands of applications that businesses rely upon in today's marketplace.

Syslogs permission not getting changed - aix 6.1

AIX


Tags
aix, unix

Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 10-02-2012
novaothers novaothers is offline
Registered User
 
Join Date: Dec 2011
Last Activity: 17 May 2013, 12:41 AM EDT
Posts: 9
Thanks: 1
Thanked 2 Times in 2 Posts
Syslogs permission not getting changed - aix 6.1

Friends,

I've tried to modify the syslogs permission by using the perm option in the syslog configuration in AIX 6.1 TL 05. But its not getting applied after the configuration. Have restarted the syslog service also.

Need your help!

The below are the conf details and os versions

Code:
[/]> oslevel -s 
6100-05-01-1016

[/]> cat /etc/syslog.conf
# @(#)34        1.11  src/bos/etc/syslog/syslog.conf, cmdnet, bos610 4/27/04 14:47:53
# IBM_PROLOG_BEGIN_TAG 
# This is an automatically generated prolog. 
#  
# bos610 src/bos/etc/syslog/syslog.conf 1.11 
#  
# Licensed Materials - Property of IBM 
#  
# COPYRIGHT International Business Machines Corp. 1988,1989 
# All Rights Reserved 
#  
# US Government Users Restricted Rights - Use, duplication or 
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
#  
# IBM_PROLOG_END_TAG 
#
# COMPONENT_NAME: (CMDNET) Network commands. 
# 
# FUNCTIONS: 
#
# ORIGINS: 27 
#
# (C) COPYRIGHT International Business Machines Corp. 1988, 1989 
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
# 
# /etc/syslog.conf - control output of syslogd
#
#
# Each line must consist of two parts:-
#
# 1) A selector to determine the message priorities to which the 
#    line applies
# 2) An action.
#
# Each line can contain an optional part:-
#
# 3) Rotation.
#
# The fields must be separated by one or more tabs or spaces.
#
# format:
#
# <msg_src_list> <destination> [rotate [size <size> k|m] [files <files>] [time <time> h|d|w|m|y] [compress] [archive <archive>]]
#
# where <msg_src_list> is a semicolon separated list of <facility>.<priority>
# where:
#
# <facility> is:
#       * - all (except mark)
#       mark - time marks
#       kern,user,mail,daemon, auth,... (see syslogd(AIX Commands Reference)) 
#
# <priority> is one of (from high to low):
#       emerg/panic,alert,crit,err(or),warn(ing),notice,info,debug
#       (meaning all messages of this priority or higher)
#
# <destination> is:
#       /filename - log to this file
#       username[,username2...] - write to user(s)
#       @hostname - send to syslogd on this machine
#       * - send to all logged in users
#
# [rotate [size <size> k|m] [files <files>] [time <time> h|d|w|m|y] [compress] [archive <archive>]] is:
#       If <destination> is a regular file and the word "rotate" is
#       specified, then the <destination> is limited by either
#       <size> or <time>, or both <size> and <time>. The <size> causes
#       the <destination> to be limited to <size>, with <files> files
#       kept in the rotation. The <time> causes the <destination> to be rotated after
#       <time>. If both <time> and <size> are specified then logfiles
#       will be rotated once the the logfile size exceeds the <size>
#       or after <time>, whichever is earlier. The rotated filenames
#       are created by appending a period and a number to <destination>,
#       starting with ".0".
#
#       If compress option is specified then the logfile names will be
#       generated with a ".Z" extension. The files keyword will be applicable
#       to the logfiles which are currently under rotation. For example
#       if we specify the compress option then only fileis with ".Z" extension
#       will be under rotation and number of such files will be limited by
#       <files> files. Any logfiles with an extension other than ".Z"
#       will not be under the rotation scheme and thus will not be within
#       the limit of <files> files. Similarly if we remove the compress
#       option then the files which have been generated with ".Z" extension
#       will no longer be the part of rotation scheme and will not be limited
#       by the <files> files.
#
#       The minimum size that can be specified is 10k, the minimum
#       number of files that can be specified is 2. The default
#       size is 1m (meg) and the default for <files> is unlimited.
#       Therefore, if only "rotate" is specified, the log will be
#       rotated with <size> = 1m.
#       The compress option means that rotated log files that are not
#       in use will be compressed.
#       The archive option will save rotated log files that are not
#       in use to <archive>.
#       The default is not to rotate log files.
#
# 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 higher, go to all users"
#  mail.debug           /usr/spool/mqueue/syslog
#  *.debug              /dev/console
#  *.crit                       *
#  *.debug              /tmp/syslog.out     rotate size 100k files 4
#  *.crit               /tmp/syslog.out     rotate time 1d
  *.debug              /var/adm/syslog.out     rotate size 100k files 4
  *.crit               /var/adm/messages     rotate size 100k files 4 
user.debug;*.emerg;*.alert;*.crit,*.err,*.warning,*.notice,*.info,*.debug /syslogs/syslog.log rotate size 3000k files 5 perm 775

[/]> ls -lrt /syslogs/ 
total 35088
drwxrwsr-x    2 root     system          512 Jun 12 23:15 lost+found
-rw-------    1 root     sys         3000038 Aug 25 06:52 syslog.log.4
-rw-------    1 root     sys         3000006 Aug 29 02:51 syslog.log.3
-rw-------    1 root     sys         3000055 Sep 01 23:27 syslog.log.2
-rw-------    1 root     sys         3000055 Sep 05 19:53 syslog.log.1
-rw-------    1 root     sys         3000009 Sep 09 16:40 syslog.log.0
-rw-------    1 root     sys         2945973 Oct 03 08:33 syslog.log

Cheers
Sponsored Links
    #2  
Old 10-02-2012
jim mcnamara jim mcnamara is offline Forum Staff  
...@...
 
Join Date: Feb 2004
Last Activity: 28 August 2014, 5:04 PM EDT
Location: NM
Posts: 10,180
Thanks: 275
Thanked 785 Times in 734 Posts
You will see the change in perms when you go to the next new file, after "log rotate".
Based on your .conf file that looks like Oct 07.
Sponsored Links
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
owner Permission changed automatically selvaforum HP-UX 6 02-08-2012 11:37 AM
How to find out who changed the file permission in unix Uttamnsd UNIX for Dummies Questions & Answers 7 01-27-2012 01:12 PM
I accidentally changed to only write permission on /usr/bin... please Help! scaryMac23 OS X (Apple) 6 02-04-2010 01:38 PM
/usr/bin has been changed with 777 permission bullz26 Solaris 5 09-03-2009 07:06 AM
How to changed Permission on Tape real-chess Linux 6 09-09-2008 08:42 AM



All times are GMT -4. The time now is 10:16 PM.