Ok. Thanks.
Sorry.
2014-08-29 6:59 GMT-03:00 Bernd Petrovitsch :
> Hi all!
>
> On Don, 2014-08-28 at 20:24 -0300, Wandeson Ricardo wrote:
> [...]
> > I'm create network/interfaces and use dhcp to get network properties but
> I
> > have not success.
>
> Ever read http://www.chiark.greenend.org.uk
Hi,
On Sat, Nov 16, 2013 at 08:48:13PM +0200, Aaro Koskinen wrote:
> less displays -E in help text, but it's not doing anything. Make it quit
> less when the last lines of the file have been printed.
>
> Signed-off-by: Aaro Koskinen
> ---
Any comments about this patch? Or should we just drop th
Il 29/08/2014 19:01, Harald Becker ha scritto:
Alfonso: Can you try this when ...
a) ... you do "ln foobar hello2" (hardlink)
b) ... you do "cp -p foobar hello3" (physical copy)
In case of a hard link or a copy, hello is not killed when foobar is killed.
___
Hi Alfonso !
Hi Denys !
This is suspicious. killall shall not kill both processes ...
> ./foobar &
cat /proc/19618/comm
foobar
cat /proc/19618/cmdline
./foobar
cat /proc/19618/status
Name: foobar
./hello &
cat /proc/19669/comm
hello
cat /proc/19669/cmdline
./hello
cat /proc/19669/status
N
Il 29/08/2014 18:17, Harald Becker ha scritto:
Hi Alfonso !
I looked in the source for Busybox killall. It compares the value of the
comm field to determine which command is running. So give the /proc
field values for comm, cmdline and status of your processes, please.
--
Harald
On funtoo:
Hi Alfonso !
I looked in the source for Busybox killall. It compares the value of the
comm field to determine which command is running. So give the /proc
field values for comm, cmdline and status of your processes, please.
--
Harald
___
busybox mai
Il 29/08/2014 17:39, Harald Becker ha scritto:
Hi Alfonso !
> > See what ps or top say for those two jobs.
You did not give the information from my question.
busybox killall foobar
My Busybox killed foobar, not hello ... just tested!
So you indeed need to look for more detail, what is li
Hi Alfonso !
> I just wanted to know if it is a "will" or "just happens" in
find_pid_by_name.
The manpage says, killall shall send the signal to all processes running
the command. In fact is, you run the same command twice, when you do
this symlinking. As different kernel versions provide di
Hi Alfonso !
> > See what ps or top say for those two jobs.
You did not give the information from my question.
busybox killall foobar
My Busybox killed foobar, not hello ... just tested!
So you indeed need to look for more detail, what is listed for the two
active processes.
--
Harald
Il 29/08/2014 17:18, Harald Becker ha scritto:> Hi Alfonso !
>
> > ln -s foobar hello
>
> I overlooked this. Sorry!
>
>> ./foobar &
>> ./hello &
>
> This way you indeed start the same application twice. Especially if they
> are shell scripts or something similar, it is very hard to distinguish
>
On Fri, Aug 29, 2014 at 05:05 PM, Harald Becker said:
> Did you verify that hello exited due to a signal from killall?
I can replicate the problem here with busybox killall but not with
the standard (Gnu?) killall. My busybox killall lives in /live/bin.
$ ln -s /bin/sleep hello
$ sleep 100 &
Hi Alfonso !
> ln -s foobar hello
I overlooked this. Sorry!
./foobar &
./hello &
This way you indeed start the same application twice. Especially if they
are shell scripts or something similar, it is very hard to distinguish
with which name they got started. See what ps or top say for thos
Hi Alfonso !
> ./foobar &
./hello &
killall foobar
also hello is killed
Did you verify that hello exited due to a signal from killall?
When a process exits the shell does not always display the information
immediately. Before display of next command prompt all job processes
which exited
Busybox git.
If I do
ln -s foobar hello
./foobar &
./hello &
killall foobar
also hello is killed
Is it a "normal" behaviour?
Thanks in advance.
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
Hi all!
On Don, 2014-08-28 at 20:24 -0300, Wandeson Ricardo wrote:
[...]
> I'm create network/interfaces and use dhcp to get network properties but I
> have not success.
Ever read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html (and fro
the bigger picture http://catb.org/~esr/faqs/smart-que
The first time i setup a busybox dhcp i forget to put the start script in my
image (example comes with documentation).
i would check
1. is dhcpd stating ?
2. do i get pakets ?
3. does the setup script start ?
re,
wh
Am 29.08.2014 01:24, schrieb Wandeson Ricardo:
> Hi Sir,
>
> Thanks to suppor
16 matches
Mail list logo
