Sponsored Content
Operating Systems HP-UX Problems after filesystem housekeeping Post 302995017 by anaigini45 on Friday 31st of March 2017 12:39:44 AM
Old 03-31-2017
Problems after filesystem housekeeping

I have noticed that after I clear up the /var filesystem, there are always problems.

Does deleting the OLDsyslog.log file cause problems like missing directories and problems accessing crontabs?

There were two situations where I faced problems.
1) Deleted OLDsyslog.log (Of course I created an archive of this before deleting).
The next day there were problems of missing directories in a path not even related to the log which is /var/adm/syslog.

2) In this situation, I also did the same - deleted old syslog, and backdated ones, and now there is another problem, whereby users are not able to access their crontab :

Code:
$ crontab -l
crontab: you are not authorized to use cron.  Sorry.
bscs.L28bi02> (/bscsbin/lisa)

And so I checked the server, and found that even the cron directory went missing! So this means that everything under cron like cron.allow was gone. I had to manually create the directory and this file for the user to be able to use it again.

Now the user can list the crontab entries, but not able to save new cron entries :
Code:
/var/tmp/aaaa15475" 277 lines, 14951 characters cron may not be running - call your system administrator

I restarted cron, then I can save the entries.

Also, I realize now that many directories in /var/adm are missing. Like /var/adm/sa, /var/adm/syslog.
I cannot even get any output from the command "last". (To check who deleted the files). The error is :

Code:
# last
 : No such file or directory


Last edited by anaigini45; 03-31-2017 at 01:53 AM..
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

housekeeping

hey, I have to write a housekeeping script which would delete any files which are more than 10 days old, the file is named in such a fashion MYTEST20060101_182239.txt MYXML20060112_182879.xml MYEXCEL20060113_546321.xls If the current date is 20060112, then MYTEST20060101_182239.txt will be... (2 Replies)
Discussion started by: mpang_
2 Replies

2. UNIX for Advanced & Expert Users

Problems filesystem

Hi, I've a Unixware 7.1.4, the machine has 3 disks, the second disk is not mounted, he said the message "WARNING: msgcnt 2 vxfs: mesg 021: vx_fs_init - /dev/dsk/c0b0t1d0s1 file system validation failure". I use the fsck command to check and repair, during the pocess apears messages to... (3 Replies)
Discussion started by: By_Jam
3 Replies

3. Shell Programming and Scripting

Filesystem Monitoring script problems

Hi there all, #!/usr/bin/ksh Set -x MIN_MB_FREE="100MB" # Min. MB of Free FS Space MAX_PERCENT="85%" # Max. FS percentage value FSTRIGGER="1000MB" # Trigger to switch from % Used to MB Free WORKFILE="/tmp/df.work" # Holds filesystem data >$WORKFILE #... (0 Replies)
Discussion started by: draco
0 Replies

4. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies

5. Shell Programming and Scripting

Housekeeping Not Working

Hi, I have a .ksh script which finds all the directories older than 84 days and tries to housekeep. Below is the command used find * -depth -type d -ctime +84 -exec rm -rf {} \; The above command lists all the directories ie child and parent directory in descending order which are more... (10 Replies)
Discussion started by: annamalai77
10 Replies

6. Shell Programming and Scripting

Housekeeping script

I have a directory ( eg. /tmp , there are many files in it , I would like to do the houskeeping job , can advise how to develop a script to do the following . 1) if the files are elder than 10 days in this directory , the extension is .txt , then move it to /tmp/tmp-txt , the same , if the files... (2 Replies)
Discussion started by: ust3
2 Replies

7. Filesystems, Disks and Memory

Filesystem Problems with DMG

Hi all! I have a task that has been giving me problems.I have my sister-in-law's external hard drive that has been damaged and the filesystem is not mountable. I am on a Mac running OSX 10.6.8 Using ddrescue, I recovered the contents and transferred to my external drive: sudo ddrescue... (0 Replies)
Discussion started by: Imhotep1963
0 Replies

8. AIX

Housekeeping null 2>&1 in /dev

Hello, Does anyone know how to housekeeping the null 2>&1 file in /dev? its fill up my system, please help. Thanks :b: (3 Replies)
Discussion started by: only
3 Replies

9. UNIX for Beginners Questions & Answers

[Tip] Housekeeping Tasks Made Easy - User Home directories and Leftover Files

We have regularly questions about how to create users and user accounts. But regularly user accounts need to be deleted too. It is quite easy to delete the user account itself but usually the HOME directory of the user remains. It is good style to remove these directories but simply deleting... (3 Replies)
Discussion started by: bakunin
3 Replies
CRONTAB(1)							   User Commands							CRONTAB(1)

NAME
crontab - maintains crontab files for individual users SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] [-i] [-s] crontab -n [ hostname ] crontab -c DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more crontabs for each range. For more information, see selinux(8). In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs. Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory. The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used. OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u command is used under his username. -l Displays the current crontab on standard output. -r Removes the current crontab. -e Edits the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. -i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab. -s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs - see the documentation of MLS_LEVEL in crontab(5). -n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied, the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run, and considered host-specific. For more information on clustering support, see cron(8). -c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using the -n option. SEE ALSO
crontab(5), cron(8) FILES
/etc/cron.allow /etc/cron.deny STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. DIAGNOSTICS
An informative usage message appears if you run a crontab with a faulty command defined in it. AUTHOR
Paul Vixie <vixie@isc.org> Colin Dean <colin@colin-dean.org> cronie 2012-11-22 CRONTAB(1)
All times are GMT -4. The time now is 05:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy