Sponsored Content
Operating Systems Solaris Can't execute logadm proberly Post 302952589 by MadeInGermany on Thursday 20th of August 2015 05:54:05 AM
Old 08-20-2015
Sometimes the better alternative is to not use the -c option,
instead signal the process to close/open its logfile by means of the -a option.
 

10 More Discussions You Might Find Interesting

1. Solaris

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... (1 Reply)
Discussion started by: dawinkler
1 Replies

2. Shell Programming and Scripting

Need to execute 2 scripts, wait, execute 2 more wait, till end of file

:cool: I need to execute a shell script to do the following: cat a file run two back ground processes using the first two values from the file wait till those background processes finish run two more background processes using the next two values from the file wait till those background... (1 Reply)
Discussion started by: halo98
1 Replies

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
fclose(3S)																fclose(3S)

NAME
fclose(), fflush(), fclose_unlocked(), fflush_unlocked() - close or flush a stream SYNOPSIS
Obsolescent Interfaces DESCRIPTION
causes any buffered data for the named stream to be written out, and the stream to be closed. Buffers allocated by the standard input/out- put system may be freed. is performed automatically for all open files upon calling exit(2). If stream points to an output stream or an update stream in which the most recent operation was output, causes any buffered data for the stream to be written to that file; otherwise any buffered data is discarded. The stream remains open. If stream is a null pointer, performs this flushing action on all currently open streams. Obsolescent Interfaces and close or flush a stream. RETURN VALUE
Upon successful completion, and return 0. Otherwise, they return EOF and set to indicate the error. ERRORS
If or fails, is set to one of: The flag is set for the file descriptor underlying stream and the process would be delayed in the write operation. The file descriptor underlying stream is not valid. An attempt was made to write a file that exceeds the process's file size limit or the maximum file size (see ulimit(2)). or was interrupted by a signal. The process is in a background process group and is attempting to write to its controlling terminal, is set, the process is neither ignoring nor blocking the signal, and the process group of the process is orphaned. There was no free space remaining on the device containing the file. An attempt was made to write to a pipe that is not open for reading by any process. A signal is also sent to the process. Additional values may be set by the underlying and functions (see write(2), lseek(2) and close(2)). WARNINGS
and are obsolescent interfaces supported only for compatibility with existing DCE applications. New multithreaded applications should use and SEE ALSO
close(2), exit(2), lseek(2), write(2), flockfile(3S), fopen(3S), setbuf(3S), thread_safety(5). STANDARDS CONFORMANCE
fclose(3S)
All times are GMT -4. The time now is 07:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy