12-12-2007
/var/tmp is designed to store "reboot persistent" temporary data. i.e. data that one may wan't to recover should the machine crash or is stopped because of a power outage, or data a program want to persist between successive runs.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Help ! - I have a process which I cannot find that is writing to /var/tmp every 10 minutes and filling up my partition, it is also filling up my wtmpx file. I have some software error correction for a faulty DIMM at the moment - is this likely to be causing this as well as over-loading my... (3 Replies)
Discussion started by: Mal
3 Replies
2. UNIX for Dummies Questions & Answers
Hello,
does anyone have a script that can check the contents of the /tmp directory and for example e-mail the directory content if anything other than session files are present?
Maybe there are better ways to monitor suspicous /tmp and /var/tmp activity, if so I'm listening :) (1 Reply)
Discussion started by: jamesbond
1 Replies
3. UNIX for Dummies Questions & Answers
I'm getting an error when trying to vi my .profile. This is the first time I've logged onto this machine and apparently its rarely logged into. I'm assuming from the error that it's a permissions problem in the /var/tmp directory. Can anyone assist?
$ uname -a
AIX machine 1 5 000D96BF4C00
$... (3 Replies)
Discussion started by: dangral
3 Replies
4. Red Hat
i heard once that the /tmp directory was a ramfs (swap) that is cleared at reboot time, is this still the case in redhat EL 3 and 4 ? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
5. Solaris
what's the impact if I change /var/tmp's permission into 750? (7 Replies)
Discussion started by: a2156z
7 Replies
6. Linux
Hi All,
Can I delete the above file? It's big, about 1G. It's on a redhat ent 4 with ldap on it.
Is that safe to delete? It wasn't been used for already a month and it's in the backup storage.
Thanks for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies
7. Solaris
this is the situation:
Power outage. Root mirror (svm).
it goes to single-user-mode, asking for fsck.
Fsck suceeds for one disk, but fail for the other.
I can't use vi-editor, it says /var/tmp/Xz12a is a read-only file system.
I need to break the mirror, there's no copy of... (2 Replies)
Discussion started by: Sun Fire
2 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
Can you please tell me the command, with which one can know the amount of space a specific directory has used.
df -k . ---> Displays, the amount of space allocated, and used for a directory.
du -k <dir name> - gives me the memory used of all the files inside <dir>
But i... (2 Replies)
Discussion started by: abhisheksunkari
2 Replies
9. Red Hat
Can anyone help me with this error?
sudo yum install perl-Gtk2-WebKit
Loaded plugins: langpacks, presto, refresh-packagekit, versionlock
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package perl-Gtk2-WebKit.i686 0:0.09-1.fc15 will be installed
-->... (0 Replies)
Discussion started by: cokedude
0 Replies
10. HP-UX
Hi,
To clear up the filesystem, I archived /var/tmp (forgot that this directory was important for crontab), and then deleted the directory itself.
After that there were problems like crontab not accessible, certain ftp commands like mget not functioning, and worst there were some scripts which... (4 Replies)
Discussion started by: anaigini45
4 Replies
LEARN ABOUT XFREE86
reboot
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)