With the root partition full it can be impossible to log in. If you are logged in as root at the time, don't log out.
The continuous error messages output to the system console can make the system console unusable. The error messages to system logs and cstm logs can cause /var to fill.
The rest depends on how your system is configured. As long as you have separate mountpoints for /usr /var /opt /tmp and /home it's often recoverable if you are quick. You must reboot after clearing the problem because the /etc/utmp file is likely to be corrupted and the system will have stopped System Accounting.
To get an idea of what might be affected:
Filling /var can be a lot more difficult to deal with.
We have SunOS 5.7 m/c. Following is the situation and problem what we are facing -
- The root partition was full.
- No login was possible on server (not from console also)
- M/c was power swithced off
- After this only console login is possible. FTP is possible. No telnet is possible.
I... (3 Replies)
We have SunOS 5.7 m/c. Following is the situation and problem what we are facing -
- The root partition was full.
- No login was possible on server (not from console also)
- M/c was power swithced off
- After this only console login is possible. FTP is possible. No telnet is possible.
I... (1 Reply)
Hi Everyone,
I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
HI,
Currently I am working in One of the webhosting company and I found
on one of my server "/home" partition is getting full say 105% usage...
But when I actually check the partition size using "du -h", exact partition
utilization is only 60-70%.
So... (1 Reply)
i am using redhat 5.4 and my root size shows 98 %, how can i increase root size
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 77G 16G 75G 98% /
/dev/sda1 2.4G 82M 2.2G 4% /boot
tmpfs 3.8G 0 3.8G 0%... (8 Replies)
My /var partition is almost utilized ... Here am not sure where to release space now
OS/model : HP-UX B.11.11 U 9000/800
# bdf /var
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol9 6144000 6142176 1824 100% /var
<root@pb>/var # du -sk * | sort -n |... (20 Replies)
Hello Folks,
Greetings,
I am in need of extending the / partition for one of my SuSE linux Enterprise Server 11.1 which is running on VMware. I will be able to extend the virtual lun from the vshphere console but not sure how to extend the root partition from the OS end. I am not sure if I... (1 Reply)
Hello guys,
I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Dear Concern,
I am new in ubuntu. Is root user disable in ubuntu? Also, is os partition default in ubuntu? I don't find any feature to create customize mount point to install OS.
Below is my current OS partition.
amirislam@blnidapp03:~$ df -h
Filesystem Size Used... (1 Reply)
Good day,
Anybody, know how to clean/free up the Cluster_boot partition in TRU64
Thank you in advance
Miaka (0 Replies)
Discussion started by: miaka1012
0 Replies
LEARN ABOUT OSF1
syslog.conf
syslog.conf(4) Kernel Interfaces Manual syslog.conf(4)NAME
syslog.conf - syslogd configuration file
SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h.
See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See
/usr/include/sys/syslog_pri.h.
The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you
specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a
host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An
asterisk (*) causes a message to be sent to all users who are currently logged in.
DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify
more than one facility and its severity level by separating them with semicolons.
You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section.
The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to
include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab
characters.
If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com-
mand: # syslogd -f config_file
Daily Log Files
You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following
syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log
file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon
creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax:
/var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file
variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre-
ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory.
To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory.
EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary #
priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys-
log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug
/var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg
*
FILES
/etc/syslog.conf
/etc/syslog.auth - Authorization file for remote logging.
/usr/include/sys/syslog_pri.h - Common components of a syslog event log record.
RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8)
System Administration delim off
syslog.conf(4)