public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Steve Beck <stevebeck99@hotmail.com>,
	"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Setting process command name in forked process
Date: Tue, 30 Jan 2024 16:10:02 +0000	[thread overview]
Message-ID: <DM8PR09MB7095534E540A52A240929800A57D2@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <DM6PR20MB347605AD07FF2C854B9BE5AAB17E2@DM6PR20MB3476.namprd20.prod.outlook.com>

> that it matters at all, I'd like to +1 the suggestion/request of picking up support for
> setproctitle(3) in the next available release.

>> in which case I'd prefer to implement this via setproctitle(3), given
>> this API exists on BSD and Linux.

Well, I don't think setproctitle(3) exists on Linux everywhere (at least not on the version that
we have around here), but I second that adding it to Cygwin would be beneficial, regardless.

prctl(PR_SET_NAME) exists on Linux but is very limited, so we can't even use it for our
purposes...  We do a hack of modifying the argv[] array, in a way different than Cygwin's, though.

Anton Lavrentiev
Contractor NIH/NLM/NCBI


  reply	other threads:[~2024-01-30 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 19:32 Steve Beck
2024-01-24 17:09 ` Brian Inglis
2024-01-26 15:47 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2024-01-26 18:35   ` Steve Beck
2024-01-29  9:58     ` Corinna Vinschen
2024-01-29 22:00       ` Steve Beck
2024-01-30 16:10         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2024-01-29 15:50     ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2024-01-29 15:57       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM8PR09MB7095534E540A52A240929800A57D2@DM8PR09MB7095.namprd09.prod.outlook.com \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@cygwin.com \
    --cc=stevebeck99@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).