| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Erik,
The format for /proc/meminfo has changed between 2.4 and 2.6, quite considerably.
In addition to the removal of the two-line summary that was present in 2.4,
MemShared was also removed. Presently (at least in busybox CVS HEAD), top fails
to parse this correctly and spews forth a:
top: failed to read 'meminfo'
message. This patch switches around some of the semantics a little to do sane
parsing for both 2.4 and 2.6. Also, in the event that the summary gets yanked
from 2.4, this patch will deal with that as well. With this patch, I'm able
to run top correctly on 2.6.0-test7 (tested on sh).
Please apply.
procps/top.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++------------
1 files changed, 48 insertions(+), 12 deletions(-)
git-svn-id: svn://busybox.net/trunk/busybox@7639 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7635 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7634 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7630 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7629 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7628 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7627 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7626 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7625 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7624 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hi Eric
I have written a small patch for the Busybox syslogd. With this patch
one can limit the size of the messagfile. As soon as the limit is
reached the syslogd can rotate or purge the messagefile(s) on his own.
There is no necessity to use an external rotatescript.
Even if logread does something similar, its very handy to have some
messagefile after your box crash.
I wrote this patch initial vor BB 0.6x where no cron daemon was avail.
Now I adapted it for the new Version and i hope it is still useful. At
least I still use it :-)
bye
Arnd
git-svn-id: svn://busybox.net/trunk/busybox@7623 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
full_write to use safe_write internally, which is needed to guarantee proper
behavior, i.e. when writing to a pipe.
git-svn-id: svn://busybox.net/trunk/busybox@7621 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7620 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
option
git-svn-id: svn://busybox.net/trunk/busybox@7619 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7618 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7605 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7601 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
| |
Moving on to building diffutils, busybox sed needs this patch to get
past the first problem. (Passing it a multi-line command line argument
with -e works, but if you don't use -e it doesn't break up the multiple
lines...)
git-svn-id: svn://busybox.net/trunk/busybox@7600 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7599 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7598 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
| |
`echo "README" | xargs ls -al`
Dont specify a path for the default behaviour of echo
args allocated space for an extra ptr
Use defines for the different options
git-svn-id: svn://busybox.net/trunk/busybox@7597 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
| |
- env vars CONTENT_TYPE, CONTENT_LENGTH, HTTPD_REFERER, REMOTE_USER and
AUTH_TYPE(Basic always).
- POST data pipied now (previous version have loading into memory may be
big size data and reducing with hardcoded limit)
- removed $CGI_foo environment variables, else my have rubbish
enviroment if POST data have big binary file
git-svn-id: svn://busybox.net/trunk/busybox@7596 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7595 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7594 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7593 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
| |
Need to chdir after the tar file is opened, so make common tar filename
parsing and send the file descriptor rather than filename to
writeTarFile.
Modify the verboseFlag operation to determine wether to display on
stderr or stdout at display time, simpler than doing it in tar_main.
git-svn-id: svn://busybox.net/trunk/busybox@7589 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7587 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7586 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7584 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
introduces a few others (but they are being worked on)
git-svn-id: svn://busybox.net/trunk/busybox@7583 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
Fix two race conditions, as described at.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=212764
git-svn-id: svn://busybox.net/trunk/busybox@7567 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
| |
Add follow mode to logread, ala "tail -f /var/log/messages"
Note: output to a slow serial terminal can have side effects
on syslog because of the semaphore. In such case, define
RC_LOGREAD.
git-svn-id: svn://busybox.net/trunk/busybox@7565 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
Patch by Padraig, resubmitted by Fillod Stephane
git-svn-id: svn://busybox.net/trunk/busybox@7564 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
busybox namespace
git-svn-id: svn://busybox.net/trunk/busybox@7563 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
debian builds
git-svn-id: svn://busybox.net/trunk/busybox@7562 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7561 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7560 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7558 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
chgrp and install.
git-svn-id: svn://busybox.net/trunk/busybox@7557 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
Linking to my_getgrnam from libpwdgrp wasnt working, instead it was
trying to use functionality from glibc, which pulled in libnss.
git-svn-id: svn://busybox.net/trunk/busybox@7549 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The construct certain vintages of GCC (the one I have trouble
with is 3.2.3) have trouble with looks like the following:
static struct st a;
static struct st *p = &a;
struct st { int foo; };
static void init(void) { a.foo = 0; }
The problem disappears if we move the struct declaration up to
let the compiler know the shape of the struct before the first
definition uses it, like this:
struct st { int foo; }; /* this has been moved up */
static struct st a;
static struct st *p = &a;
static void init(void) { a.foo = 0; }
git-svn-id: svn://busybox.net/trunk/busybox@7537 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
| |
or the posix standard.
Put the cleanup code back the way it was.
git-svn-id: svn://busybox.net/trunk/busybox@7535 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
a test for it.
git-svn-id: svn://busybox.net/trunk/busybox@7534 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7533 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7532 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"If the shell is compiled with -DJOBS, this is all fine -- find wasn't
stopped (it was killed), so it correctly uses WTERMSIG instead of WSTOPSIG.
However, if the shell _isn't_ compiled with -DJOBS (which it isn't in d-i),
only WSTOPSIG is used, which extracts the high byte instead of the low
byte from the status code. Since the status code is 13 (SIGPIPE), "st"
suddenly gets the value 0, which is equivalent to SIGEXIT. Thus, ash prints
out "EXIT" on find's exit."
git-svn-id: svn://busybox.net/trunk/busybox@7531 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
1788 bytes (for strings.o).
git-svn-id: svn://busybox.net/trunk/busybox@7530 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
| |
git-svn-id: svn://busybox.net/trunk/busybox@7529 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unless it had #!/bin/sh in the first line
"It correctly locates the script, tries to execute it via execve which
fails. After that it tries to hand it over to /bin/sh which fails too,
since ash
- neither provides the absolute pathname to /bin/sh
- nor tries to lookup the script via PATH if called as "sh script"
"
git-svn-id: svn://busybox.net/trunk/busybox@7528 69ca8d6d-28ef-0310-b511-8ec308f3f277
|
|
|
|
|
|
|
| |
----------------------------------------------------------------------
git-svn-id: svn://busybox.net/trunk/busybox@7527 69ca8d6d-28ef-0310-b511-8ec308f3f277
|