08-23-2005
Just an idea: regularily cycle through the home directories and take snapshots of the command history files.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I was just going thru the auditing script ..
2 questions pop in mind .. Why did they move S81volmgmt .. What is the logic behind not loading it ..
2) Why the purpose of the device allocate entries (2 Replies)
Discussion started by: DPAI
2 Replies
2. AIX
Background:
I a trying to audit user administration on a AIX box. I am trying to make sure that any changes made by the System administrator to the user accounts (Add users, changing their attributes or deleting users) are accompanied by authorization i.e. the system admin does not make any... (0 Replies)
Discussion started by: gladiator
0 Replies
3. HP-UX
Hi all
I hope to find what i'm looking for in this forum
as said in the topic i want to track user's actions on the system. i mean also the action of moving or removing files. I have an HP 9000 with HP UX 11i. the users log on the HP from a terminal window under WIndows XP
Thx (3 Replies)
Discussion started by: Timberland
3 Replies
4. Solaris
How do I setup audit to alert on write conditions for individual files? Thanks. (3 Replies)
Discussion started by: dxs
3 Replies
5. UNIX for Advanced & Expert Users
:)I need a little help. I have sent all of our logs to our log server, but I can't send the audit logs that are in /var/log/audit.log. Can someone give me some type of idea to transfer these logs.
Thank You (2 Replies)
Discussion started by: aojmoj
2 Replies
6. Shell Programming and Scripting
Hi All,
I need to put in place a UNIX shell script that calls three sql scripts & reports to the DBAs.
I already have the three sql scripts in place & they perform the following database auditing actions:
1. actions.sql
This script queries the DBA_AUDIT _TRAIL table to look for database user... (2 Replies)
Discussion started by: divroro12
2 Replies
7. Shell Programming and Scripting
Hello,
is there some way to track what shell commands some user is executing ?
Something like to have some log file where i could see what commands some user used, e.g. rm -r dirname , ls -l .... and so on ...
I have 2.6.13-1.1526_FC4smp (9 Replies)
Discussion started by: tonijel
9 Replies
8. Solaris
Hello,
I was wondering when Solaris auditing is enabled, If it is possible to keep track of users that are allowed to sudo to root. In other words, I would like to know which user did what on my Solaris box. (assumig that user can "sudo su -" )
Thanks. (2 Replies)
Discussion started by: niyazi
2 Replies
9. AIX
In our customer place somebody removed and PV from the server. I want the information like which user removed this PV.
Is there any way to get PV removal information.
When did the PV removed from the server ?
Whether AIX auding will help ?
Where i can get these information ?
Thank... (2 Replies)
Discussion started by: sunnybee
2 Replies
10. AIX
I am trying to find out the information of my local desktop when i use putty to login to an AIX server.
This is what I do:
1. login to my PC
2. take a putty session to an AIX server
Can i get information of my local desktop from the AIX server ? Is there a command available ?
Thanks (8 Replies)
Discussion started by: Nagesh_1985
8 Replies
LEARN ABOUT CENTOS
snapper-configs
SNAPPER-CONFIGS(5) Filesystem Snapshot Management SNAPPER-CONFIGS(5)
NAME
snapper-configs - Configuration files for snapper configs
DESCRIPTION
Each file /etc/snapper/configs/* describes a snapper config.
VARIABLES
The following is a list of variables that can be present in the configuration file. Boolean values must be "yes" or "no".
SUBVOLUME=path
Path of the subvolume or mount point.
There is no default value. The value must always be specified.
FSTYPE=value
Filesystem type for the subvolume.
Default value is "btrfs" but it's recommended to always specify the filesystem type.
ALLOW_USERS=users
List of users allowed to operate with the config. The user-names must be separated by spaces. Spaces in usernames can be escaped with a
"".
Default value is "" but "root" is always implicitly included.
ALLOW_GROUPS=groups
List of groups allowed to operate with the config. The group-names must be separated by spaces. Spaces in group-names can be escaped
with a "".
Default value is "".
BACKGROUND_COMPARISON=boolean
Defines whether pre and post snapshots should be compared in the background after creation.
Default value is "no".
NUMBER_CLEANUP=boolean
Defines whether the number cleanup algorithm should be run for the config.
Default value is "no".
NUMBER_MIN_AGE=seconds
Minimal age for snapshots to be deleted by the number cleanup algorithm.
Default value is "1800".
NUMBER_LIMIT=number
Defines how many snapshots the number cleanup algorithm should keep. The youngest snapshots will be kept.
Default value is "50".
TIMELINE_CREATE=boolean
Defines whether hourly snapshots should be created.
Together with the timeline cleanup algorithm this will create a collection of snapshots with more snapshots is the near past and less
snapshots in the far past.
Default value is "no".
TIMELINE_CLEANUP=boolean
Defines whether the timeline cleanup algorithm should be run for the config.
Default value is "no".
TIMELINE_MIN_AGE=seconds
Minimal age for snapshots to be deleted by the timeline cleanup algorithm.
Default value is "1800".
TIMELINE_LIMIT_HOURLY=number
Defines how many hourly snapshots the timeline cleanup algorithm should keep. An hourly snapshots is the first snapshot in an hour. The
youngest hourly snapshots will be kept.
Default value is "10".
TIMELINE_LIMIT_DAILY=number
Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The
youngest daily snapshots will be kept.
Default value is "10".
TIMELINE_LIMIT_MONTHLY=number
Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The
youngest daily snapshots will be kept.
Default value is "10".
TIMELINE_LIMIT_YEARLY=number
Defines how many daily snapshots the timeline cleanup algorithm should keep. A daily snapshots is the first snapshot in a day. The
youngest daily snapshots will be kept.
Default value is "10".
EMPTY_PRE_POST_CLEANUP=boolean
Defines whether the empty-pre-post cleanup algorithm should be run for the config.
Default value is "no".
EMPTY_PRE_POST_MIN_AGE=seconds
Minimal age for snapshots to be deleted by the empty-pre-post cleanup algorithm.
Default value is "1800".
HOMEPAGE
http://snapper.io/
AUTHORS
Arvin Schnell <aschnell@suse.de>
SEE ALSO
snapper(8), snapperd(8)
0.1.7 2013-07-09 SNAPPER-CONFIGS(5)