Opened 23 years ago
Closed 20 years ago
#418 closed defect (fixed)
procps-3.2.6
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
I couldn't find a dedicated bug for procps (not surprising considering how long .7 has been out), anyways check the URL for details and such.
Attachments (1)
Change History (65)
comment:1 by , 23 years ago
| dependson: | → 30 |
|---|
comment:2 by , 23 years ago
| Priority: | low → high |
|---|
comment:3 by , 23 years ago
| Priority: | high → lowest |
|---|
comment:4 by , 23 years ago
| Summary: | procps-2.0.8 → procps-2.0.9 |
|---|
Version increment (2.0.9);
"Sep 30, 2002 Friday's release has awoken some other procps developers, many patches have been integrated over the weekend and it's time for a new release: procps-2.0.9.tar.bz2."
comment:5 by , 23 years ago
| Summary: | procps-2.0.9 → procps-2.0.10 |
|---|
Version increment (2.0.10);
- fix memory size overflow in ps (Anton Blanchard)
- add iowait statistics to top (Rik van Riel)
- update top help text (Denis Vlasenko)
- fix jumpy percentage formatting in top (Denis Vlasenko)
- fix some newer gcc compiler warnings (Denis Vlasenko)
- by default, do not show threads in ps or top - you can use the
-m' flag in ps or theH' key in top to show them (Robert Love)
comment:6 by , 23 years ago
There's been a mail to lkml by Albert D. Calahan that procps, "contrary to popular belief", is still maintained. They've just released version 3.0.1. The address is http://procps.sourceforge.net/
comment:8 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Summary: | procps-3.0.1 → procps-3.0.4 |
comment:9 by , 23 years ago
| bug_file_loc: | http://surriel.com/procps/ |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | procps-3.0.4 → procps-3.0.5 |
Version increment (3.0.5);
Uh, just want to mention quickly, we never had a discussion about which version to stay with, either 2.1.x or 3.0.x. As they are both different projects now, with the same name and everything, I think it best to at least take a closer look then just using the one with a bigger version number :)
comment:10 by , 23 years ago
| Summary: | procps-3.0.5 → procps-3.1.1|2.0.10 |
|---|
comment:11 by , 23 years ago
| Summary: | procps-3.1.1|2.0.10 → procps-3.1.2|2.0.10 |
|---|
Version increment (3.1.2)
comment:12 by , 23 years ago
| Summary: | procps-3.1.2|2.0.10 → procps-3.1.2|2.0.11 |
|---|
Version increment (2.0.11)
comment:13 by , 23 years ago
| Summary: | procps-3.1.2|2.0.11 → procps-3.1.3|2.0.11 |
|---|
Version increment (3.1.3)
comment:14 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:15 by , 23 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.3|2.0.11 → procps-3.1.4|2.0.11 |
Version increment (3.1.4)
comment:16 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:17 by , 23 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.4|2.0.11 → procps-3.1.5|2.0.11 |
Version increment (3.1.5)
comment:18 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:19 by , 23 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.5|2.0.11 → procps-3.1.6|2.0.11 |
Version increment (3.1.6)
comment:20 by , 23 years ago
| Summary: | procps-3.1.6|2.0.11 → procps-3.1.7|2.0.11 |
|---|
Version increment (3.1.7)
comment:21 by , 23 years ago
| Summary: | procps-3.1.7|2.0.11 → procps-3.1.8|2.0.11 |
|---|
Version increment (3.1.8)
comment:22 by , 23 years ago
version incroment for v2 to 2.0.12 new location for v2 ONLY: http://tech9.net/rml/procps/ could someone update the summary (i havnt got the perms to do it)
comment:23 by , 23 years ago
| Summary: | procps-3.1.8|2.0.11 → procps-3.1.8|2.0.12 |
|---|
Version increment (2.0.12)
comment:24 by , 23 years ago
| Priority: | lowest → highest |
|---|
comment:25 by , 23 years ago
| Status: | reopened → assigned |
|---|
comment:26 by , 23 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:27 by , 22 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.8|2.0.12 → procps-3.1.9|2.0.12 |
Version increment (3.1.9)
comment:28 by , 22 years ago
| Summary: | procps-3.1.9|2.0.12 → procps-3.1.9|2.0.13 |
|---|
Version increment (2.0.13)
comment:29 by , 22 years ago
| Summary: | procps-3.1.9|2.0.13 → procps-3.1.11|2.0.13 |
|---|
Version Increment (3.1.11)
comment:30 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:31 by , 22 years ago
| Summary: | procps-3.1.11|2.0.13 → procps-3.1.11|2.0.14 |
|---|
Version increment (2.0.14);
Still no decision on which is going to be used? (could have sworn I read an e- mail/thread on this recently, hrm)
comment:32 by , 22 years ago
| Priority: | highest → lowest |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | procps-3.1.11|2.0.14 → procps-3.1.12|2.0.14 |
Version increment (3.1.12) - dropping to P5 so I don't try and fix this during the package-freeze :)
comment:33 by , 22 years ago
http://downloads.linuxfromscratch.org/procps-3.1.11.patch still applies cleanly to this version.
comment:34 by , 22 years ago
This package is obviously maintained (at least the 3.1.x version). Is there any reason why we need to keep on maintaining the patch?
Surely, if the patch is correct and can be demonstrated to be so, then upstream would accept it and save us the hassle of maintaining it ourselves.
Any takers?
comment:35 by , 22 years ago
| Summary: | procps-3.1.12|2.0.14 → procps-3.1.13|2.0.14 |
|---|
Version increment (3.1.13)
comment:36 by , 22 years ago
| Summary: | procps-3.1.13|2.0.14 → procps-3.1.14|2.0.14 |
|---|
Version increment (3.1.14)
comment:37 by , 22 years ago
I've researched the current patch for procps. I cannot reproduce the problem, nor can I see how it's relevant after studying the source code. Here are some relevant threads from the archives:
http://archives.linuxfromscratch.org/mail-archives/lfs-dev/2001-October/020595.html http://linuxfromscratch.org/pipermail/lfs-support/2002-January/002195.html http://linuxfromscratch.org/pipermail/lfs-support/2002-January/002251.html
Essentially, upstream ended up applying locale fixes to proc/sysinfo.c. The current patch is therefore bogus and is just historical baggage. I will remove this patch at next package update.
comment:38 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Upgrade committed and patch dropped.
comment:39 by , 22 years ago
| dependson: | 30 |
|---|
comment:40 by , 22 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.14|2.0.14 → procps-3.1.15|2.0.18 |
Version increment (3.1.15/2.0.18) - apologies for incrementing both couldn't remember whether we had a discussion as to which version we want to use and a search didn't appear to give a definite 3.x or 2.x choice.
comment:41 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
apologies for incrementing both couldn't remember whether we had a discussion to which version we want to use and a search didn't appear to give a definite 3.x or 2.x choice.
There doesn't appear to be any pressing reason to use the 2.x version for now. The 3.x version continues to be maintained and updated so best to stick with what we know works IMHO.
comment:42 by , 22 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.1.15|2.0.18 → procps-3.2.0 |
Version increment (3.2.0) - fixes for 2.6.4 (when we migrate over).
comment:43 by , 22 years ago
| Status: | reopened → assigned |
|---|
comment:44 by , 22 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:45 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:46 by , 22 years ago
comment:47 by , 22 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.2.0 → procps-3.2.1 |
comment:49 by , 21 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.2.1 → procps-3.2.2 |
Version increment (3.2.2)
comment:50 by , 21 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:51 by , 21 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.2.2 → procps-3.2.3 |
Version increment (3.2.3). From News:
--- procps-3.2.2 --> procps-3.2.3
avoid truncating long usernames avoid warning about -lncurses when not linking (more) new names for shared libraries (packagers: watch out!) "make install" no longer rebuilds everything wchan now '*' for multi-threaded processes ps: new man page -- thanks Nicolas Francois ps: STAT shows l for multi-threaded processes vmstat: some overflow problems fixed -- thanks Holger Kiehl sysctl: man page fix ---
Additionally, http://linuxfromscratch.org/pipermail/lfs-dev/2004-August/048179.html mentions that we no longer need to 'rm /lib/libproc.so'.
comment:53 by , 21 years ago
| Version: | CVS → TESTING |
|---|
comment:54 by , 21 years ago
and no longer trying to remove the non-existant /lib/libproc.so in unstable
comment:55 by , 21 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:56 by , 21 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.2.3 → procps-3.2.4 |
Version increment (3.2.4) - thanks Jim! Note there's a new command ('pwdx') with this one.
comment:58 by , 21 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Summary: | procps-3.2.4 → procps-3.2.5 |
Version increment (3.2.5)
comment:59 by , 21 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:60 by , 20 years ago
| Priority: | lowest → normal |
|---|---|
| Resolution: | fixed |
| Status: | closed → reopened |
| Summary: | procps-3.2.5 → procps-3.2.6 |
| Version: | TESTING → SVN |
Version increment (3.2.6)
comment:61 by , 20 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:62 by , 20 years ago
| Status: | new → assigned |
|---|
comment:63 by , 20 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
comment:64 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |

Just a note - I've added this to bug #30's dependency list.
Secondly, although we really should update procps before LFS-4.0 (our version is ridiculously stale), we shouldn't do it yet because shortly after the release, Rik van Riel posted this to LKML:
On Fri, 27 Sep 2002, Rik van Riel wrote:
Does anybody have a brown paper bag I could borrow ?
It appears Robert and I cleaned up stuff a bit too much and procps lost it's VERSION string, so -V doesn't work in the tarball I released earlier today.
Also, it appears the release has awoken some long sleeping patches, which I'll read and (if they work) integrate into procps.
Expect patches and maybe even a fixed 2.0.8 tarball soon...
If you have any procps bugs or patches, please mail the procps team:
regards,
Rik
So hopefully we can go to the next release (which it appears should be soon) well in time for LFS-4.0 [I know Gerard said don't do package updates but I feel this is a special case due to the old version being fairly out of date]