Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Oct 2011 16:58:50 +0200
From:      n dhert <ndhertbsd@gmail.com>
To:        Polytropon <freebsd@edvax.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Fwd: FreeBSD 8.2, sec.update -p3, switching between X and console prompt, /var full
Message-ID:  <CAEFCw4vE2pp0Ko=wD7AHdg8hVxH5duncVFCuhNuQpFCvnq5NGg@mail.gmail.com>
In-Reply-To: <20111003153640.b7072af9.freebsd@edvax.de>
References:  <CAEFCw4tiopWb2zSO390r8wTxK_=kTjd=d+yiBaQ97q1S163sRA@mail.gmail.com> <4E89AED9.3000705@my.gd> <CAEFCw4vXDzW7VMBQ_uRBHyOd2fYT0QG66mNAMRxAf65QFECx7g@mail.gmail.com> <CAEFCw4tTX-yAC2TL75JevXw--s-cna1TL3_RZPXAgJrvqUZRyQ@mail.gmail.com> <20111003153640.b7072af9.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
I tried
# ps -jaxw | grep X
root        7609  1461  7609     1    1 S     ??    0:00.55 /usr/local/bin/X
-br -nolisten tcp :0 -auth /var/run/xauth/A:0-9mN8YK (
root        7633  3423  7632  3356    2 S+     5    0:00.06 grep X
# kill -9 7609

but it creates a new one ...
# ps -jawx | grep X
root        7640  1461  7640     1    1 S     ??    0:00.69 /usr/local/bin/X
-br -nolisten tcp :0 -auth /var/run/xauth/A:0-9mN8YK (

I killed the parent process /usr/local/bin/kdm-bin
now /var is back to normal in du -ks  (19%)

But still no reaction on Cltrl-Alt-F*  keystrokes.






2011/10/3 Polytropon <freebsd@edvax.de>

> On Mon, 3 Oct 2011 15:15:26 +0200, n dhert wrote:
> > I tried Ctrl-Alt-Backspace in the graphical login wndow, but as with
> other
> > key Ctrl-Alt key combinations
> > this does not do anything ...
>
> It is "new behaviour" that certain default functionalities
> of X need to be enabled manually. Ctrl+Alt+Backspace is one
> of them, and Ctrl+Alt+F1/2/3/... _may_ be too.
>
> If I remember correctly, /etc/X11/xorg.conf requires
>
>        Section "ServerLayout"
>                Option "DontZap" "false"
>        EndSection
>        Section "ServerFlags"
>                Option "DontVTSwitch" "false"
>        EndSection
>
> to re-enable the default behaviour. But check the Handbook
> for detailed information.
>
>
>
> > I there a commadn line way to restart X
>
> You can kill the X process. Dirty stuff, but works. :-)
>
>
>
> > I also tried fsck-ing the /var/ file system, but it chooses  NO WRITE
> > nothing is repaired
>
> You cannot run fsck on a mounted file system. You'll have
> to unmount /var first, _then_ issue the fsck command. You
> should do that in single user mode. Reason: If you have
> unmounted /var, but some process wants to write to /var,
> the empty mountpoint residing on / will be filled, therefore
> / will be filled which is _not_ intended.
>
>
>
> > See the last UNREF FILE, it has the size of the huge /var/log/Xorg.0.log
> I
> > already deleted from command line (and not anymore in
> > an ls -la), but keeps fulling /var
>
> Additionally to using rm, you can also use fsdb to "forcedly
> delete files" under worst circumstances.
>
> Removing files should be done after booting the system in
> single user mode. This way you can make _sure_ nothing is
> writing to those files. Before a removal attempt, you should
> run fsck so the file system is in a valid condition.
>
>
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAEFCw4vE2pp0Ko=wD7AHdg8hVxH5duncVFCuhNuQpFCvnq5NGg>