Help, everything on the screen is blue!

Ashley Benton meggalen at
Wed Nov 7 03:18:50 UTC 2007

Thanks your answer helped me to better understand what I read, I had been
reading the man lsof for the last hour or more but would have had to do it
again before to have been to understand it enough. A lot of different
options certainly very good when you know what you want and what you need,
but I recognize that without help that won't be for me, at least not before
a few months of study.
Bon appetit

On 11/6/07, Rapael Morcha <raphael.morcha at> wrote:
> On Tue, Nov 06, 2007 at 07:39:47PM -0500, Ashley Benton wrote:
> > No I tried it before to answer to you but as you guess that was a little
> too
> > difficult to understand, and I didn't want to look for hours before to
> ......................
> It seems you need to at least invest 5 mins reading documentation on top
> and lsof.
> man top lsof;
> If you don't like the smell of manpages, Google is your friend. In
> particular you need the process ID of the process or the processes name to
> be able to kill it.
> Process id is PID 2578 run by user called root and the processes name is
> /sbin/udevd (udev daemon, a background process).
> raphael at f9:[~] lsof |less
> COMMAND     PID       USER   FD      TYPE     DEVICE     SIZE
> NODE          NAME
> udevd      2578       root  mem       REG        8,2    61872
> 294916        /sbin/udevd
> Similarly process id is PID with parent process id (PPID) of 1 (init) and
> the command is /sbin/udevd --daemon.
> raphael at f9:[~] ps -ef | less
> UID        PID  PPID  C STIME TTY          TIME CMD
> root      2578     1  0 Nov06 ?        00:00:00 /sbin/udevd --daemon
> If I want to kill PID 2578, I'd do -
> raphael at f9:[~] kill 2578
> If I want to kill PID 2578, I could do -
> raphael at f9:[~] kill -9 2578
> In this e.g., "-9" signifies a unix signal called "KILL" (see man kill for
> more info on that).
> Debating and throwing someones anger at someone else in this list does no
> benefit to anyone. Keep it gooood and clean Ubuntians. ;) Also, telling as
> much information as possible when posting to get solution helps everyone
> trying to answer one's problem. "I have a problem with my screen, I can't do
> this, that" sort of question helps no one. Keep it cool. :)

I couldn't tell anything except the change of color because I had no idea
why it did it. I only knew what I did before but couldn't see the  rapport
between the two. I still have no idea what had caused the change of screen
color and why everything came back to normal after I did lsof, since I just
wrote it on the terminal tried to read it, then close it to open the man
page. When I opened the man page the screen was back to normal. Anyway thank
you for the help, save me a difficult time to read and study with the

I am off to lunch. Too hungry. :)
> --
> Cheers,
> Raphael.
> --
> ubuntu-users mailing list
> ubuntu-users at
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ubuntu-users mailing list