Skip to content

The "uptime" cmd from the default config is not working #1197

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.

Sign up for GitHub

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

Jump to bottom
Closed
ezradiniz opened this issue Mar 5, 2022 · 4 comments · May be fixed by #1718
Closed

The "uptime" cmd from the default config is not working #1197

ezradiniz opened this issue Mar 5, 2022 · 4 comments · May be fixed by #1718
Labels
🐛 bug "Houston, we've had a problem."

Comments

@ezradiniz
Copy link

What's broken?

The uptime cmd is not working properly, it is showing exit status 1

But it works if I remove the empty string "" from the args:

args: [""]
cmd: "uptime"

Args without ""

args: []
cmd: "uptime"
@senorprogrammer senorprogrammer added the 🐛 bug "Houston, we've had a problem." label Mar 8, 2022
@FelicianoTech
Copy link
Contributor

What version of wtf are you running?
What's your OS and OS version?

This is working for me out of the box so I'm trying to determine what might be different here.

@brandonwardlaw
Copy link

Same issue here. Noted tweak above works for me.

System info:

❯ uname -a
Linux <hostname> 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
❯ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04 LTS
Release:        22.04
Codename:       jammy
❯ wtfutil --version
0.41.0 (2021-12-28T22:54:23Z)

Seanstoppable added a commit to Seanstoppable/wtf that referenced this issue Aug 14, 2022
@Seanstoppable
Remove 'blank' arg from default configs
b2b8869 
From wtfutil#1197, this seems to break on linux
Thought is that on linux this is translating into some weird extra arg
Since we can have a blank args list, I think this makes sense to keep it blank
@Seanstoppable Seanstoppable mentioned this issue Aug 14, 2022
Merged
Seanstoppable added a commit to Seanstoppable/wtf that referenced this issue Aug 15, 2022
@Seanstoppable
Remove 'blank' arg from default configs
724b3e8 
From wtfutil#1197, this seems to break on linux
Thought is that on linux this is translating into some weird extra arg
Since we can have a blank args list, I think this makes sense to keep it blank
Seanstoppable added a commit that referenced this issue Aug 15, 2022
@Seanstoppable
Remove 'blank' arg from default configs (#1296)
20c682e 
From #1197, this seems to break on linux
Thought is that on linux this is translating into some weird extra arg
Since we can have a blank args list, I think this makes sense to keep it blank
@umop3plsdn
Copy link

just wanted to comment and say this issue still exists for some reason with a new install

@toby-bro
Copy link

Yes it is because of this :

wtf/cfg/default_config_file.go

Lines 93 to 94 in 6a02b97

uptime:
args: [""]

did you do a local install with go install . to install wtf ?

@toby-bro toby-bro mentioned this issue Mar 29, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 bug "Houston, we've had a problem."
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: remove empty args string from default config toby-bro/wtf
7 participants
@senorprogrammer @umop3plsdn @Seanstoppable @FelicianoTech @brandonwardlaw @ezradiniz @toby-bro