osutil: implement setprocname to set process title for some platforms This patch adds a simple setprocname method to osutil. The operation is not defined by any standard and is platform-specific, the current implementation tries to cover some major platforms (ex. Linux, OS X, FreeBSD) that is relatively easy to support. Other platforms (Windows [4], other BSDs, ...) can be added in the future. The current implementation supports two methods to change process title: a. setproctitle if available (works in FreeBSD). b. rewrite argv in place (works in Linux [1] and Mac OS X). [2] [3] [1]: Linux has "prctl(PR_SET_NAME, ...)" but 1) it has 16-byte limit, which is too small; 2) it is not quite equivalent to what we want - it changes "/proc/self/comm", not "/proc/self/cmdline" - "comm" change won't show up in "ps" output unless "-o comm" is used. [2]: The implementation does not rewrite the **environ buffer like some other implementations do, just to make the code simpler and safer. However, this also means the buffer size we can rewrite is significantly shorter. If we are really greedy and want the "environ" space, we can change the implementation later. [3]: It requires a CPython private API: Py_GetArgcArgv to get the original argv. Unfortunately Python 3 makes a copy of argv and returns the wchar_t version, so it is not supported for now. (if we really want to, we could count backwards from "char **environ", given known argc and argv, not sure if that's a good idea - probably not) [4]: The feature is aimed to make it easier for forked command server processes to show what they are doing. Since Windows does not support fork(), despite it's a major platform, its support is not added in this patch.

     1

# Base Revsets to be used with revsetbenchmarks.py script

     2

#

     3

# The goal of this file is to gather a limited amount of revsets that allow a

     4

# good coverage of the internal revsets mechanisms.  Revsets included should not

     5

# be selected for their individual implementation, but for what they reveal of

     6

# the internal implementation of smartsets classes (and their interactions).

     7

#

     8

# Use and update this file when you change internal implementation of these

     9

# smartsets classes. Please include a comment explaining what each of your

    10

# addition is testing. Also check if your changes to the smartset class makes

    11

# some of the tests inadequate and replace them with a new one testing the same

    12

# behavior.

    13

#

    14

# If you want to benchmark revsets predicate itself, check 'all-revsets.txt'.

    15

#

    16

# The current content of this file is currently likely not reaching this goal

    17

# entirely, feel free, to audit its content and comment on each revset to

    18

# highlight what internal mechanisms they test.

    19

    20

all()

    21

draft()

    22

::tip

    23

draft() and ::tip

    24

::tip and draft()

    25

0::tip

    26

roots(0::tip)

    27

author(lmoscovicz)

    28

author(mpm)

    29

author(lmoscovicz) or author(mpm)

    30

author(mpm) or author(lmoscovicz)

    31

tip:0

    32

0::

    33

# those two `roots(...)` inputs are close to what phase movement use.

    34

roots((tip~100::) - (tip~100::tip))

    35

roots((0::) - (0::tip))

    36

42:68 and roots(42:tip)

    37

::p1(p1(tip))::

    38

public()

    39

:10000 and public()

    40

draft()

    41

:10000 and draft()

    42

roots((0:tip)::)

    43

(not public() - obsolete())

    44

(_intlist('20000\x0020001')) and merge()

    45

parents(20000)

    46

(20000::) - (20000)

    47

# The one below is used by rebase

    48

(children(ancestor(tip~5, tip)) and ::(tip~5))::