Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unrecognized command or argument 'list-processes' #1570

Closed
sunny868 opened this issue Sep 16, 2020 · 6 comments · Fixed by #1575
Closed

Unrecognized command or argument 'list-processes' #1570

sunny868 opened this issue Sep 16, 2020 · 6 comments · Fixed by #1575

Comments

@sunny868
Copy link

Description

$ dotnet-trace list-processes
Required command was not provided.
Unrecognized command or argument 'list-processes'

Configuration

dotnet-trace --version
3.1.141901+3f460984c62efa118b6bd87fa4c5f07b11074b34

uname -a
Linux localhost.localdomain 4.19.73+ dotnet/runtime#2 SMP PREEMPT Fri May 15 11:29:21 CST 2020 mips64 mips64 mips64 GNU/Linux

@Dotnet-GitSync-Bot
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Sep 16, 2020

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

sunny868 referenced this issue in sunny868/runtime Sep 16, 2020
@tommcdon tommcdon transferred this issue from dotnet/runtime Sep 16, 2020
@sywhang
Copy link
Contributor

sywhang commented Sep 17, 2020

list-processes has been renamed to ps a while ago. I'm not sure if this issue is regarding adding support for the list-processes command, or something else?

@sunny868
Copy link
Author

I found there are many list-processes exist at path /doc . Can you replace list-processes in the document with ps ?

@sywhang
Copy link
Contributor

sywhang commented Sep 17, 2020

Ah, yes. I will go ahead and update those docs. Thank you for the feedback!

@sunny868
Copy link
Author

That would be great !

@ghost ghost locked as resolved and limited conversation to collaborators Jun 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants