Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] cpulimit segmentation fault
@ 2024-03-13  8:03 ACR-Jeff
  2024-03-13 15:04 ` [ISSUE] [CLOSED] " Johnnynator
  2024-03-13 18:07 ` ACR-Jeff
  0 siblings, 2 replies; 3+ messages in thread
From: ACR-Jeff @ 2024-03-13  8:03 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

New issue by ACR-Jeff on void-packages repository

https://github.com/void-linux/void-packages/issues/49270

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.18_1 x86_64 AuthenticAMD uptodate rmFFFFFFFF

### Package(s) Affected

cpulimit-0.2_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

The latest I could find is back in 2016 in cpulimit issues https://github.com/opsengine/cpulimit/issues?q=segmentation+fault

Maybe this will help get some info to resolve with the void-package, I solved it temporarily by Downloading an updated version `cpulimit_2.8-1_amd64.deb` from debian bookworm packages and installing with xdeb `https://github.com/xdeb-org/xdeb`

### Expected behaviour

Expecting `cpulimit --exe=processname -l 500` (changing 'processname' with actual process name) to limit a process to not use over the 500 value of cpu usage.

### Actual behaviour

When using cpulimit and a set of arguments example: `cpulimit --exe=processname -l 500` within the terminal it prints 'Segmentation Fault'. I have tested also with `sudo cpulimit -e=processname -l 500` which has the same results.

### Steps to reproduce

1. Installing cpulimit `./xbps-src pkg cpulimit`
2. sudo xbps-install -R hostdir/binpkgs cpulimit
3. Execute a process to test cpulimit
4. Open Terminal
5. exec cpulimit within terminal `cpulimit --exe=processname -l 500` 
6. changing 'processname' with actual process name before executing
7. Results `Segmentation Fault`

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ISSUE] [CLOSED] cpulimit segmentation fault
  2024-03-13  8:03 [ISSUE] cpulimit segmentation fault ACR-Jeff
@ 2024-03-13 15:04 ` Johnnynator
  2024-03-13 18:07 ` ACR-Jeff
  1 sibling, 0 replies; 3+ messages in thread
From: Johnnynator @ 2024-03-13 15:04 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

Closed issue by ACR-Jeff on void-packages repository

https://github.com/void-linux/void-packages/issues/49270

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.18_1 x86_64 AuthenticAMD uptodate rmFFFFFFFF

### Package(s) Affected

cpulimit-0.2_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

The latest I could find is back in 2016 in cpulimit issues https://github.com/opsengine/cpulimit/issues?q=segmentation+fault

Maybe this will help get some info to resolve with the void-package, I solved it temporarily by Downloading an updated version `cpulimit_2.8-1_amd64.deb` from debian bookworm packages and installing with xdeb `https://github.com/xdeb-org/xdeb`

### Expected behaviour

Expecting `cpulimit --exe=processname -l 500` (changing 'processname' with actual process name) to limit a process to not use over the 500 value of cpu usage.

### Actual behaviour

When using cpulimit and a set of arguments example: `cpulimit --exe=processname -l 500` within the terminal it prints 'Segmentation Fault'. I have tested also with `sudo cpulimit -e=processname -l 500` which has the same results.

### Steps to reproduce

1. Installing cpulimit `./xbps-src pkg cpulimit`
2. sudo xbps-install -R hostdir/binpkgs cpulimit
3. Execute a process to test cpulimit
4. Open Terminal
5. exec cpulimit within terminal `cpulimit --exe=processname -l 500` 
6. changing 'processname' with actual process name before executing
7. Results `Segmentation Fault`

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: cpulimit segmentation fault
  2024-03-13  8:03 [ISSUE] cpulimit segmentation fault ACR-Jeff
  2024-03-13 15:04 ` [ISSUE] [CLOSED] " Johnnynator
@ 2024-03-13 18:07 ` ACR-Jeff
  1 sibling, 0 replies; 3+ messages in thread
From: ACR-Jeff @ 2024-03-13 18:07 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 180 bytes --]

New comment by ACR-Jeff on void-packages repository

https://github.com/void-linux/void-packages/issues/49270#issuecomment-1995223383

Comment:
Thank you @Johnnynator Works great!

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-03-13 18:07 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-13  8:03 [ISSUE] cpulimit segmentation fault ACR-Jeff
2024-03-13 15:04 ` [ISSUE] [CLOSED] " Johnnynator
2024-03-13 18:07 ` ACR-Jeff

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 NNTP newsgroup(s).