> # inotifyd /home/piotr/myhandler /var/tmp/myfiles/data:M
>
> The 'data' file exists. New file 'data_tmp' is created. 'data_tmp' is
> renamed to 'data'.
>
I think you've chosen the wrong event. Filename is just a "tag", it is
inodes that are looked for events. (Correct me if I'm wrong, guys)
Tr
# inotifyd /home/piotr/myhandler /var/tmp/myfiles/data:M
The 'data' file exists. New file 'data_tmp' is created. 'data_tmp' is renamed
to 'data'.
Piotr
No change. Still no M.
Strange enough.
Let me see how you call inotifyd.
--
Vladimir
__
Your example works for me too.
Piotr
> On Friday 14 November 2008 23:02, Piotr Grudzinski wrote:
>> No change. Still no M.
>
> Works for me:
>
> # ./busybox inotifyd echo TODO_config_nommu
> M TODO_config_nommu
>
> (I did "mv TODO_config_nommu TODO_config_nommu.x")
> --
> vda
___
> No change. Still no M.
>
Strange enough.
Let me see how you call inotifyd.
--
Vladimir
___
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
> Having 11 letters for other events I tried letter 'O' for 'unwrittable
> file is closed' which failed. A zero was
> expected which I find interesting: why one number and eleven letters?
>
0 (zero) stands for "nothing". I presumed closing a read-only file as
"nothing has changed". Thus the nam
On Friday 14 November 2008 23:02, Piotr Grudzinski wrote:
> No change. Still no M.
Works for me:
# ./busybox inotifyd echo TODO_config_nommu
M TODO_config_nommu
(I did "mv TODO_config_nommu TODO_config_nommu.x")
--
vda
___
busybox mailing list
busybox@
On Friday 14 November 2008 23:04, Vladimir Dronnikov wrote:
> > You must dispose of your own zombies, or set SIGCHLD to SIG_IGN.
> > the second is a semi-official Linux extension
>
>
> I'm concerned primarily to Linux.
>
>
> > Setting SIGCHLD to SIG_IGN would make inotifyd to fire-and-forget
>
Having 11 letters for other events I tried letter 'O' for 'unwrittable file is
closed' which failed. A zero was
expected which I find interesting: why one number and eleven letters?
:-)
Piotr
3. Was the number zero intended to be used for the 'unwrittable file is
closed' event?
Didn't ca
>
> You need to say so in help text.
I almost didn't touch inotifyd since it was born. The time has come, since
active users appear.
> Moreover, some users won't like it.
> They might want to get these events in a serialized fashion.
I suppose it is a least surprising behavior.
> No. init s
No change. Still no M.
BR,
Piotr
2. The letter M - for the 'self is moved' event - is never passed to my
agent script; the script runs but there is nothing printable in the 1st
parameter.
I'll take closer a look.
Seems we had classic buffer overflow :)
Will you try attached pat
On Friday 14 November 2008 21:58, Vladimir Dronnikov wrote:
> > 1. Every time my agent script runs, a new zombie process is left behind.
> > The same script runs cleanly with a cron program. (this is not the busybox
> > cron).
> >
>
> A zombie is a terminated process which is not wait()ed by its p
>
> 2. The letter M - for the 'self is moved' event - is never passed to my
>> agent script; the script runs but there is nothing printable in the 1st
>> parameter.
>>
>
> I'll take closer a look.
>
Seems we had classic buffer overflow :)
Will you try attached patch?
> Regards,
> --
> Vladimir
>
>
> Here are my problems with inotifyd applet:
>
Let us take a look.
> 1. Every time my agent script runs, a new zombie process is left behind.
> The same script runs cleanly with a cron program. (this is not the busybox
> cron).
>
A zombie is a terminated process which is not wait()ed by its p
Hi,
I am running busybox 1.12.1 on uClinux (from uClinux.org) on ARM9 nommu system.
Here are my problems with inotifyd applet:
1. Every time my agent script runs, a new zombie process is left behind. The
same script runs cleanly with a cron program. (this is not the busybox cron).
2. The letter
On Friday 14 November 2008 09:42:50 walter harms wrote:
> hhhmmm,
>
> releasing a code that depends on a libc version that is not released yet
> it not nice to users.
I suspect glibc had this years ago and that's what they were testing against.
I also note that uClibc had an -rc1, -rc2, and -rc3
Hi,
I recently started to use the busybox HTTP server and I found that
that the CGI environment passed to scripts is incomplete.
While the CGI spec ( http://hoohoo.ncsa.uiuc.edu/cgi/env.html ) says
"the header lines received from the client [...] are placed into the
environment with the prefix H
hhhmmm,
releasing a code that depends on a libc version that is not released yet
it not nice to users.
something like
if uClibc version < 0.9.30
you need version 0.9.30 at least
exit
end if
may help also.
re,
wh
Rob Landley schrieb:
> On Tuesday 11 November 2008 23:44:32 Ha
17 matches
Mail list logo
