Uploaded image for project: 'OpenVZ'
  1. OpenVZ
  2. OVZ-6408

man for vzctl about numfile should be fixed

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: OpenVZ-legacy
    • Component/s: Containers::Userspace
    • Security Level: Public
    • Environment:
      Operating System: Other
      Platform: Other

      Description

      Denis Lunev said:
      a ne nado stavit' bar'er == limit
      ono vydeljaet kvantami do bar'era i perehodit k chestnoj vydache posle
      kvant ot 5 do 10 deskriptorov na protsess

      but in man one can see:
      --numfile items[:items]
                 Maximum number of open files. Setting the barrier and the limit to different values does not make practical sense.

        Activity

        Hide
        kir Kir Kolyshkin added a comment - - edited

        So, is the man page correct then it says "Setting the barrier and the limit to
        different values does not make practical sense"?

        Show
        kir Kir Kolyshkin added a comment - - edited So, is the man page correct then it says "Setting the barrier and the limit to different values does not make practical sense"?
        Hide
        xemul Pavel Emelyanov added a comment - - edited

        (In reply to comment #7)
        > So, is the man page correct then it says "Setting the barrier and the limit to
        > different values does not make practical sense"?
        >

        Close enough.

        Show
        xemul Pavel Emelyanov added a comment - - edited (In reply to comment #7) > So, is the man page correct then it says "Setting the barrier and the limit to > different values does not make practical sense"? > Close enough.
        Hide
        kir Kir Kolyshkin added a comment - - edited

        OK maybe in the man page we could write something like

        "Setting the barrier to 0 effectively disables pre-charging optimization for this beancounter in the kernel, which leads to the held value being precise but could slightly degrade file open performance."

        What do you think?

        Show
        kir Kir Kolyshkin added a comment - - edited OK maybe in the man page we could write something like "Setting the barrier to 0 effectively disables pre-charging optimization for this beancounter in the kernel, which leads to the held value being precise but could slightly degrade file open performance." What do you think?
        Hide
        kir Kir Kolyshkin added a comment - - edited
        Show
        kir Kir Kolyshkin added a comment - - edited Fixed in GIT: http://git.openvz.org/?p=vzctl;a=commit;h=babb31e796bea35263bd1e8b07df610ff8842fae Will be available in vzctl >= 3.0.24
        Hide
        sergeyb Sergey Bronnikov added a comment -

        Bug was fixed more than one year ago and there were no complains from reporter after fix. We believe bug fix helped and mark bug as closed.

        Show
        sergeyb Sergey Bronnikov added a comment - Bug was fixed more than one year ago and there were no complains from reporter after fix. We believe bug fix helped and mark bug as closed.

          People

          • Assignee:
            kir Kir Kolyshkin
            Reporter:
            coolthecold@gmail.com CoolCold
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: