Date: Thu, 21 Jul 2011 22:22:23 GMT From: Eugen Konkov <kes-kes@yandex.ru> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/159095: when /var is full can not connect to server through ssh, or su Message-ID: <201107212222.p6LMMNAJ014392@red.freebsd.org> Resent-Message-ID: <201107212230.p6LMU9tj082646@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 159095 >Category: misc >Synopsis: when /var is full can not connect to server through ssh, or su >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Jul 21 22:30:09 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Eugen Konkov >Release: >Organization: ISP FreeLine >Environment: >Description: WISHLIST: allow sshd to work when /var is full. this is critical because of there is no any barrier to allow user to log in and do something (empty /var from dust). but now this does not work because of log message is tryed to be writed to 'log'.... but /var is full and loggining is stale ((( this problem is typical for 'su' also. when you logged in and try to 'su' when /var/ is full -- you are in stale. # df -h /dev/ad1s1d 989M 989M -79M 109% /var $ su Password: ...... bla bla bla, I am stale..... >How-To-Repeat: fill /var/ and try to login through ssh >Fix: write login message to file, when user is logged already. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201107212222.p6LMMNAJ014392>