Difference between revisions of "/var/"

From GhostBSD Wiki
Jump to: navigation, search
(Created page with "{{Welcome}} {|class="wikitable" style="width:96.5%;background:#FFFFFF; border:2px solid #008000;text-align:left;padding: 10px" |- ! scope="col" style="width: 100px;"|'''Dire...")
 
(Content)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Welcome}}
 
{{Welcome}}
 +
 +
==Introduction==
 +
 +
''/var'' stands for "variable" and is a standard sub-directory of the root directory in Unix-like operating systems that contains files to which the system writes data during the course of its operation. <br/>
 +
A memory-based file system is sometimes mounted at <code>/var</code>. This can be automated using the varmfs-related variables in [https://www.freebsd.org/cgi/man.cgi?query=rc.conf&sektion=5&manpath=freebsd-release-ports rc.conf(5)] or with an entry in <code>/etc/fstab</code>; refer to [https://www.freebsd.org/cgi/man.cgi?query=mdmfs&sektion=8&manpath=freebsd-release-ports mdmfs(8)] for details.
 +
 +
==Content==
  
 
{|class="wikitable" style="width:96.5%;background:#FFFFFF; border:2px solid #008000;text-align:left;padding: 10px"  
 
{|class="wikitable" style="width:96.5%;background:#FFFFFF; border:2px solid #008000;text-align:left;padding: 10px"  
Line 6: Line 13:
 
! scope="col" style="width: 350px;"|'''Description'''
 
! scope="col" style="width: 350px;"|'''Description'''
 
|-
 
|-
|x
+
|/var/account||Process accounting is a security method in which an administrator may keep track of system resources used and their allocation among users, provide for system monitoring, and minimally track a user's commands. '''On GhostBSD no content'''
|x
+
|-
 +
|/var/agentx||'''On GhostBSD no content'''
 +
|-
 +
|/var/at||Two folder: /var/at/jobs; /var/at/spool; '''On GhostBSD no content'''
 +
|-
 +
|/var/audit||'''On GhostBSD no content'''
 +
|-
 +
|/var/authpf||'''On GhostBSD no content'''
 +
|-
 +
|/var/backups||'''On GhostBSD no content'''
 +
|-
 +
|/var/cache||Application cache data; [https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s05.html /var/cache] is intended for cached data from applications. Such data is locally generated as a result of time-consuming I/O or calculation. The application must be able to regenerate or restore the data. Unlike /var/spool, the cached files can be deleted without data loss. The data must remain valid between invocations of the application and rebooting the system.
 +
 
 +
Files located under /var/cache may be expired in an application specific manner, by the system administrator, or both. The application must always be able to recover from manual deletion of these files (generally because of a disk space shortage). No other requirements are made on the data format of the cache directories.
 +
|-
 +
|/var/crash||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s06.html System crash dumps]; This directory holds system crash dumps. As of the date of this release of the standard, system crash dumps were not supported under Linux but may be supported by other systems which may comply with the FHS.
 +
|-
 +
|/var/cron||The cron utility searches /var/cron/tabs for crontab files which are  named after accounts in /etc/passwd; crontabs found are loaded into memory.
 +
|-
 +
|/var/db||'' /var/db'' contains information about the specified file
 +
|-
 +
|/var/empty||'''On GhostBSD no content'''
 +
|-
 +
|/var/games||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s07.html Variable game data]; Any variable data relating to games in ''/usr'' should be placed here. ''/var/games'' should hold the variable data previously found in ''/usr''; static data, such as help text, level descriptions, and so on, must remain elsewhere, such as ''/usr/share/games''.
 +
|-
 +
|/var/heimdal||'''On GhostBSD no content'''
 +
|-
 +
|/var/lib||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s08.html Variable state information]; This hierarchy holds state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation, and the specific file hierarchy used to store the data must not be exposed to regular users.
 +
|-
 +
|/var/log||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s10.html Log files and directories]; This directory contains miscellaneous log files. Most logs must be written to this directory or an appropriate subdirectory.
 +
|-
 +
|/var/mail||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s11.html User mailbox files]; The mail spool must be accessible through /var/mail and the mail spool files must take the form <username>. User mailbox files in this location must be stored in the standard UNIX mailbox format.'''On GhostBSD no content'''
 +
|-
 +
|/var/msgs||'''On GhostBSD no content'''
 +
|-
 +
|/var/preserve||'''On GhostBSD no content'''
 +
|-
 +
|/var/run||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html Run-time variable data]; This directory was once intended for system information data describing the system since it was booted. These functions have been moved to /run; this directory exists to ensure compatibility with systems and software using an older version of this specification.
 +
|-
 +
|/var/rwho||'''On GhostBSD no content'''
 +
|-
 +
|/var/spool||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s14.html Application spool data]; ''/var/spool'' contains data which are awaiting some kind of later processing. Data in ''/var/spool'' represents work to be done in the future (by a program, user, or administrator); often data is deleted after it has been processed.
 +
|-
 +
|/var/tmp||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html Temporary files preserved between system reboots]; The ''/var/tmp'' directory is made available for programs that require temporary files or directories that are preserved between system reboots. Therefore, data stored in /var/tmp is more persistent than data in ''/tmp''.
 +
 
 +
Files and directories located in ''/var/tmp'' must not be deleted when the system is booted. Although data stored in ''/var/tmp'' is typically deleted in a site-specific manner, it is recommended that deletions occur at a less frequent interval than ''/tmp''.
 +
 
 +
|-
 +
|/var/unbound||datai conf.d '''On GhostBSD no content'''
 +
|-
 +
|/var/yp||[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s16.html Network Information Service (NIS) database files]; Variable data for the Network Information Service (NIS), formerly known as the Sun Yellow Pages (YP), must be placed in this directory.
 
|-
 
|-
 
!colspan="2"|'''Back to ''' [[image:Icon Disti GhostBSD.png|50px|link=Directory Structure]]'''Directory Structure'''
 
!colspan="2"|'''Back to ''' [[image:Icon Disti GhostBSD.png|50px|link=Directory Structure]]'''Directory Structure'''

Latest revision as of 15:14, 24 March 2020

Welcome to Icon Disti GhostBSD.png /var/.

Introduction[edit]

/var stands for "variable" and is a standard sub-directory of the root directory in Unix-like operating systems that contains files to which the system writes data during the course of its operation.
A memory-based file system is sometimes mounted at /var. This can be automated using the varmfs-related variables in rc.conf(5) or with an entry in /etc/fstab; refer to mdmfs(8) for details.

Content[edit]

Directory Description
/var/account Process accounting is a security method in which an administrator may keep track of system resources used and their allocation among users, provide for system monitoring, and minimally track a user's commands. On GhostBSD no content
/var/agentx On GhostBSD no content
/var/at Two folder: /var/at/jobs; /var/at/spool; On GhostBSD no content
/var/audit On GhostBSD no content
/var/authpf On GhostBSD no content
/var/backups On GhostBSD no content
/var/cache Application cache data; /var/cache is intended for cached data from applications. Such data is locally generated as a result of time-consuming I/O or calculation. The application must be able to regenerate or restore the data. Unlike /var/spool, the cached files can be deleted without data loss. The data must remain valid between invocations of the application and rebooting the system.

Files located under /var/cache may be expired in an application specific manner, by the system administrator, or both. The application must always be able to recover from manual deletion of these files (generally because of a disk space shortage). No other requirements are made on the data format of the cache directories.

/var/crash System crash dumps; This directory holds system crash dumps. As of the date of this release of the standard, system crash dumps were not supported under Linux but may be supported by other systems which may comply with the FHS.
/var/cron The cron utility searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory.
/var/db /var/db contains information about the specified file
/var/empty On GhostBSD no content
/var/games Variable game data; Any variable data relating to games in /usr should be placed here. /var/games should hold the variable data previously found in /usr; static data, such as help text, level descriptions, and so on, must remain elsewhere, such as /usr/share/games.
/var/heimdal On GhostBSD no content
/var/lib Variable state information; This hierarchy holds state information pertaining to an application or the system. State information is data that programs modify while they run, and that pertains to one specific host. Users must never need to modify files in /var/lib to configure a package's operation, and the specific file hierarchy used to store the data must not be exposed to regular users.
/var/log Log files and directories; This directory contains miscellaneous log files. Most logs must be written to this directory or an appropriate subdirectory.
/var/mail User mailbox files; The mail spool must be accessible through /var/mail and the mail spool files must take the form <username>. User mailbox files in this location must be stored in the standard UNIX mailbox format.On GhostBSD no content
/var/msgs On GhostBSD no content
/var/preserve On GhostBSD no content
/var/run Run-time variable data; This directory was once intended for system information data describing the system since it was booted. These functions have been moved to /run; this directory exists to ensure compatibility with systems and software using an older version of this specification.
/var/rwho On GhostBSD no content
/var/spool Application spool data; /var/spool contains data which are awaiting some kind of later processing. Data in /var/spool represents work to be done in the future (by a program, user, or administrator); often data is deleted after it has been processed.
/var/tmp Temporary files preserved between system reboots; The /var/tmp directory is made available for programs that require temporary files or directories that are preserved between system reboots. Therefore, data stored in /var/tmp is more persistent than data in /tmp.

Files and directories located in /var/tmp must not be deleted when the system is booted. Although data stored in /var/tmp is typically deleted in a site-specific manner, it is recommended that deletions occur at a less frequent interval than /tmp.

/var/unbound datai conf.d On GhostBSD no content
/var/yp Network Information Service (NIS) database files; Variable data for the Network Information Service (NIS), formerly known as the Sun Yellow Pages (YP), must be placed in this directory.
Back to Icon Disti GhostBSD.pngDirectory Structure