Sponsored Content
Operating Systems Solaris crontab logadm vs. logchecker in Solaris 10 Post 91289 by dawinkler on Wednesday 30th of November 2005 05:33:12 PM
Old 11-30-2005
crontab logadm vs. logchecker in Solaris 10

We are upgrading netra servers from Solaris 8 to Solaris 10. With Solaris 8 we've been running /etc/cron.d/logchecker and /usr/lib/newsyslog in crontab. I understand that starting with Solaris 9 log rotation is now done with /usr/sbin/logadm.

Does anyone know how the Solaris upgrade will handle the crontab?

Will it wipe the old log rotation scripts and insert logadm (with some default conf file I assume)?

Or will it leave logchecker and newsyslog in crontab and I'll need to remove them myself?

Any info would be appreciated.

(I am looking forward to Solaris 10, but change is hard Smilie )
 

10 More Discussions You Might Find Interesting

1. Solaris

logadm package

Does anyone know what package logadm is part of? It's not on my Solaris 9 machine, I presume because I only have a core installation. But I'd like to ad it. Any help would be appreciated. (1 Reply)
Discussion started by: syscity
1 Replies

2. Solaris

logadm

I have a log file that I want to rotate each day without keeping old copies. how to achieve that? thx (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

3. Solaris

Problems with logadm / syslog in Sol 9/10

Hello folks, I've been making some changes to logadm.conf, but I'm not getting quite the results that I'm expecting /var/log/pool/poold -a 'pkill -HUP poold; true' -N -s 512k /var/svc/log/*.log -C 8 -N -s 1m /var/adm/messages -a 'pkill -HUP `cat /var/run/syslog.pid`' -C 8 -s 10m... (10 Replies)
Discussion started by: avronius
10 Replies

4. Solaris

crontab in solaris

hi I want to run a script every 30 minutes in Solaris 10 x86 I tried 0,30 * * * * /tmp/script.sh but it does not run. any idea? (1 Reply)
Discussion started by: melanie_pfefer
1 Replies

5. Solaris

Couple logadm questions

My logadm.conf is below. Is there a way to match a log file that appends the time/date stamp after the log file? Also, a 0 is being appended onto the files I'm compressing and having rotated. Is there a way to fix that? /var/apache/tomcat55/logs/catalina.out -C 30 -P 'Fri Jun 18 16:48:55... (5 Replies)
Discussion started by: LittleLebowski
5 Replies

6. Solaris

LOGADM

Dear experts. I was wondering if logadm preserves ACL setuped on for instance, /var/log/authlog. From man : ...by creating an empty file whose owner, group ID, and permissions match the original file.... Is this ACL inclusive or i need to use -a option (run cmd after... (1 Reply)
Discussion started by: Peasant
1 Replies

7. Solaris

logadm rotates log every time

I'm running logadm manually to test and it seems to be rotating my /var/log/oracle/oracle_audit.log file every single time it's ran instead of rotating once it gets passed 10 gigs, any ideas? Here's the logadm.conf for reference. (0 Replies)
Discussion started by: thmnetwork
0 Replies

8. Shell Programming and Scripting

Logadm

I need to delete the logs using logadm command. we have application that generates to logs automatically with different dates every day like error_20121121.log and so on... using lodadm can i delete the logs of last 10 days using crontabentry? i am confuse here becasue if we use logadm what... (1 Reply)
Discussion started by: phani4u
1 Replies

9. Solaris

How to logrotate a file after X days with logadm?

Hi Guys - We have the /var/adm/pacct file currently configured to log rotate using logadm - here is the entry in logadm.conf: /var/adm/pacct -C 0 -N -P 'Wed Oct 23 08:00:00 2013' -a '/usr/lib/acct/accton pacct' -g adm -m 664 -o adm -p never Just want to ask if it would like possible to... (1 Reply)
Discussion started by: akaterasu
1 Replies

10. Solaris

Can't execute logadm proberly

Hello, I am trying to rotate my logs using logadm, so I did the following logadm -w /traces/mylogs.out -C 5 -p 1d -o user -g group -m 644 -c -t '/traces/mylogs.out.$n' -z 1 and then tried to test it by logadm -v and it gets stuck at truncation step # processing logname: /traces/mylogs.out... (5 Replies)
Discussion started by: eng_asa
5 Replies
CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME
crontab -- maintain crontab files for individual users (V3) SYNOPSIS
crontab [-u user] file crontab [-u user] { -l | -r | -e } DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have their own crontab, and they are not intended to be edited directly. (Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8), which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.) If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the /usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the /usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com- ments. The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given. The following options are available: -u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you should always use the -u option for safety's sake. -l Display the current crontab on standard output. -r Remove the current crontab. -e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified crontab will be installed automatically. FILES
/usr/lib/cron/cron.allow /usr/lib/cron/cron.deny DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line. SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1) STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax. AUTHORS
Paul Vixie <paul@vix.com> BSD
December 29, 1993 BSD
All times are GMT -4. The time now is 06:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy