01-08-2008
ps -ef|grep syslog
Find the process id - do a kill -HUP on the process id
Example only:
# ps -ef|grep syslog
root 759 1 0 Jan 02 ? 0:01 /usr/sbin/syslogd
root 3344 1 0 Jan 07 ? 0:02 grep syslog
# kill -HUP 759
You might want to check any local zones /etc/syslog.conf also.
9 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When I try to log in as root I get the following message
realloccg /: file system full sendmail :NO Queue:low on space (have 0,SMTP-DAEMON needs 101 in /var/spool/mqueue) What should I do? (1 Reply)
Discussion started by: hopeless
1 Replies
2. UNIX for Advanced & Expert Users
Hi All,
There was a background process running on a Solaris 2.8 machine, and appeared to have filled all available disk-space. I done a killall, and upon re-booting found that the file system had filled up, and will not boot as normal as a result. For example, I'm getting
/usr/adm/messages: No... (8 Replies)
Discussion started by: Breen
8 Replies
3. Solaris
Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies
4. Solaris
I read the sticky and thought of a script I use on a regular basis. Since unless you patch/upgrade the df command on solaris you have a very tought time teling how full the system truly is.
Output looks like
$ biggest.sh /tmp
Filesystem kbytes used avail capacity Mounted... (0 Replies)
Discussion started by: meyerder
0 Replies
5. Solaris
hello
Even though I am not out of inodes or of space, the /var/adm/messages shows messages:
file system full
I am doing now fcsk -m (400G) and I am still waiting to see the fragmentation results (should I add another option to df to have a faster output?)
Do you have any other hints... (6 Replies)
Discussion started by: melanie_pfefer
6 Replies
6. AIX
Guy's
There is file in AIX called applog related to application and it's owned by root:system
I want normal user called appuser to mange this file without change the file owner and without add the appuser in root group
Is there any way to give this user appuser full Control in that file applog ?... (8 Replies)
Discussion started by: ITHelper
8 Replies
7. Red Hat
Hey all,
What do you think mostly happened in the following situation?
I have a Red Hat 5.5 server. Someone, somehow, managed to get two .nfs000.... type files that totaled over a terabyte in size. I removed them and thought things were back to normal. Then I started getting complains from... (2 Replies)
Discussion started by: geelsu
2 Replies
8. UNIX for Dummies Questions & Answers
Hi I was wondering if it would be possible to get the full octal permissions of a file by using something in the stat() system call. Can this be done without going through all of the seperate permissions (e.g. read for user, write for user .... etc.)? also how can this octal permission be changed... (5 Replies)
Discussion started by: bjhum33
5 Replies
9. AIX
AIX Version 6.1 and 7.1.
I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device.
It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
LEARN ABOUT PLAN9
warn.conf
warn.conf(4) File Formats warn.conf(4)
NAME
warn.conf - Kerberos warning configuration file
SYNOPSIS
/etc/krb5/warn.conf
DESCRIPTION
The warn.conf file contains configuration information specifying how users will be warned by the ktkt_warnd daemon about ticket expiration
on a Kerberos client. Credential expiration warnings are sent, by means of syslog, to auth.notice. All other warning messages are sent to
daemon.notice.
Each Kerberos client host must have a warn.conf file in order for users on that host to get Kerberos warnings from the client. Entries in
the warn.conf file must have the following format:
principal syslog | terminal | mail time [email_address]
principal Specifies the principal name to be warned. The asterisk (*) wildcard can be used to specify groups of principals.
syslog Sends the warnings to the system's syslog. Depending on the /etc/syslog.conf file, syslog entries are written to the
/var/adm/messages file and/or displayed on the terminal.
terminal Sends the warnings to display on the terminal.
mail Sends the warnings as email to the address specified by email_address.
time Specifies how much time before the TGT expires when a warning should be sent. The default time value is seconds, but you
can specify h (hours) and m (minutes) after the number to specify other time values.
email_address Specifies the email address at which to send the warnings. This field must be specified only with the mail field.
EXAMPLES
Example 1: Specifying warnings
The following warn.conf entry
* syslog 5m
specifies that warnings will be sent to the syslog five minutes before the expiration of the TGT for all principals. The form of the mes-
sage is:
jdb@ACME.COM: your kerberos credentials expire in 5 minutes
FILES
/usr/lib/krb5/ktkt_warnd Kerberos warning daemon
SEE ALSO
ktkt_warnd(1M), syslog.conf(4), SEAM(5)
SunOS 5.10 22 Apr 2003 warn.conf(4)