From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: /proc/<pid>/{cwd,root} links to <defunct> for cygrunsrv, daemons, and shells
Date: Sun, 7 Apr 2024 13:34:55 -0600 [thread overview]
Message-ID: <0df79ac3-02ea-4180-8177-375407dee2a1@SystematicSW.ab.ca> (raw)
ISTM anomalous that for cygrunsrv, daemons, cron processes, and shells
/proc/<pid>/{cwd,root} have bad symlinks to "<defunct>", normally a process or
exe status:
/proc/732/exe -> /usr/bin/cygrunsrv
/proc/732/root -> <defunct>
/proc/732/cwd -> <defunct>
| /proc/733/exe -> /usr/sbin/cygserver
->/proc/733/root -> <defunct>
/proc/733/cwd -> <defunct>
/proc/740/exe -> /usr/bin/cygrunsrv
/proc/740/root -> <defunct>
/proc/740/cwd -> <defunct>
| /proc/741/exe -> /usr/sbin/syslog-ng
->/proc/741/root -> <defunct>
/proc/741/cwd -> <defunct>
/proc/748/exe -> /usr/bin/cygrunsrv
/proc/748/root -> <defunct>
/proc/748/cwd -> <defunct>
| /proc/749/exe -> /usr/sbin/cron
->/proc/749/root -> <defunct>
/proc/749/cwd -> <defunct>
| /proc/2080/exe -> /usr/sbin/cron
->/proc/2080/root -> <defunct>
/proc/2080/cwd -> <defunct>
| /proc/2082/exe -> /usr/bin/bash
->/proc/2082/root -> <defunct>
/proc/2082/cwd -> <defunct>
Should we consider changing that to root "/", or nothing, null, or something
meaningful?
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2024-04-07 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 19:34 Brian Inglis [this message]
2024-04-09 13:08 ` /proc/<pid>/{cwd, root} " Corinna Vinschen
2024-04-09 16:38 ` Brian Inglis
2024-04-09 21:24 ` Corinna Vinschen
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=0df79ac3-02ea-4180-8177-375407dee2a1@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.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).