Difference between revisions of "/run/"

From wikieduonline
Jump to navigation Jump to search
Tags: Mobile web edit, Mobile edit
 
(5 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
  [[/run/systemd/]]
 
  [[/run/systemd/]]
 
  [[/run/systemd/system]]
 
  [[/run/systemd/system]]
  /run/[[lock]]
+
  [[/run/lock]]
 
  [[/run]]/p[[acct]]_source
 
  [[/run]]/p[[acct]]_source
 
  [[/run/nginx.pid]]
 
  [[/run/nginx.pid]]
 
  [[/run/php/]]php7.2-fpm.sock
 
  [[/run/php/]]php7.2-fpm.sock
 
  [[/run/rpcbind.sock]]   
 
  [[/run/rpcbind.sock]]   
 +
[[/run/utmp]]
  
 
  Jan 26 16:23:34 SERVER [[systemd-logind]][876]: Failed to save user data /run/systemd/users/0: [[No space left on device]]
 
  Jan 26 16:23:34 SERVER [[systemd-logind]][876]: Failed to save user data /run/systemd/users/0: [[No space left on device]]
Line 37: Line 38:
 
* <code>[[/dev/shm]]</code>
 
* <code>[[/dev/shm]]</code>
 
* <code>[[/var/run/]]</code>
 
* <code>[[/var/run/]]</code>
 +
* <code>[[/tmp/]]</code>
  
 
== See also ==
 
== See also ==
 
* {{run}}
 
* {{run}}
* {{proc}}
+
* {{FHS}}
* {{systemd}}
 
 
 
 
 
  
 
[[Category:Linux]]
 
[[Category:Linux]]

Latest revision as of 10:04, 25 August 2023

/run/ is a "tmpfs" file system for system packages to place runtime data in. This directory is flushed on boot, and generally writable for privileged programs only. Always writable.

/run/
/run/systemd/
/run/systemd/system
/run/lock
/run/pacct_source
/run/nginx.pid
/run/php/php7.2-fpm.sock
/run/rpcbind.sock   
/run/utmp
Jan 26 16:23:34 SERVER systemd-logind[876]: Failed to save user data /run/systemd/users/0: No space left on device


apt upgrade
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 1.9M are free, but a safety buffer of 16.0M is enforced.


Increase /run filesystem space

1) Append to /etc/fstab
 echo "none /run tmpfs defaults,size=256M 0 0" >> /etc/fstab
2) mount /run
3) mount -o remount /run
4) Check /run space: df -h /run
reboot
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to talk to init daemon.


Activities[edit]

Related terms[edit]

 Apr 13 07:42:02 SERVER systemd[1]: nginx.service: Failed to parse PID from file /run/nginx.pid: Invalid argument

See also[edit]

Advertising: