The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

vim sessions use 100% CPU

Discussion in 'General Discussion' started by n1zyy, Jul 17, 2004.

  1. n1zyy

    n1zyy Member

    Joined:
    Mar 16, 2003
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    1
    I'm wondering if this is a common issue or not. Every now and then our server will seem really sluggish, so I'll hop in over ssh, and top shows that a vim process uses 99.9% of our CPU, bringing our load average to 1.5 or so.

    The crazy vim processes seem to be after someone's been editing something (with vim); I don't think they're randomly starting. Does anyone know what causes this? Is there a way to proactively stop these, rather than just killing them? (They won't respond to signal 15; you have to use 9.)
     
  2. dgbaker

    dgbaker Well-Known Member
    PartnerNOC

    Joined:
    Sep 20, 2002
    Messages:
    2,578
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Toronto, Ontario Canada
    cPanel Access Level:
    DataCenter Provider
    It's usually because someone does not exit vim properly, you'll need to educate them on the proper way to exit vim. ;)
     
  3. n1zyy

    n1zyy Member

    Joined:
    Mar 16, 2003
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    1
    They usually come from one of the administrators (most other users don't even know what SSH is). He definitely mastered the :wq thing several years ago. :)

    In fact... how do you uncleanly exit vi? Pounding Ctrl+C, Ctrl+D, or Ctrl+Q repeatedly didn't do anything.
     
  4. dgbaker

    dgbaker Well-Known Member
    PartnerNOC

    Joined:
    Sep 20, 2002
    Messages:
    2,578
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Toronto, Ontario Canada
    cPanel Access Level:
    DataCenter Provider
    CTRL+Z and forgetting about will cause this.

    Losing your SSH session in the middle of editing will cause this.

    DO - locate .swp to find all files that have been edit by vim and not exited cleanly.



    Those are some other ways.
     
Loading...
Similar Threads - vim sessions 100%
  1. boing
    Replies:
    2
    Views:
    206

Share This Page