On Fri, Jun 14, 2013 at 09:26:49AM +0800, majianpeng wrote:
> Hi all,
> I wanted to monitor /proc/partitions using inotify.
That, indeed, is a bug. Easily fixed - don't do that.
> But when i call 'cat /proc/partitions',the program can't return.
> So i added some message in ker
Hi all,
I wanted to monitor /proc/partitions using inotify.Although now i know it
can't catch the event of write.
But for read,it can't catch. The code is:
int main()
{
int fd = inotify_init();
int wd;
char buff[4096];
int ret;
if (fd < 0)
Hi all,
I wanted to monitor /proc/partitions using inotify.Although now i know it
can't catch the event of write.
But for read,it can't catch. The code is:
int main()
{
int fd = inotify_init();
int wd;
char buff[4096];
int ret;
if (fd 0)
On Fri, Jun 14, 2013 at 09:26:49AM +0800, majianpeng wrote:
Hi all,
I wanted to monitor /proc/partitions using inotify.
That, indeed, is a bug. Easily fixed - don't do that.
But when i call 'cat /proc/partitions',the program can't return.
So i added some message in kernel in order
it exits.
> >er... ptrace(2)?
>
> Should work for most common usage scenarios, although will suspect that it
> won't for for processes owned by another user (at least, I hope
> it wouldn't).
>
> What is dangerous about inotify on a proc file?
And if it's dangerous, should the in
On Tue, 31 Jul 2007 20:31:49 +0200 Diego Calleja <[EMAIL PROTECTED]> wrote:
> El Mon, 30 Jul 2007 22:25:21 -0500, Joseph Pingenot <[EMAIL PROTECTED]>
> escribió:
>
> > More background, please?
> >
> > What's the way to check for a process exiting without spinning?
>
>
> I don't know if it's
El Mon, 30 Jul 2007 22:25:21 -0500, Joseph Pingenot <[EMAIL PROTECTED]>
escribió:
> More background, please?
>
> What's the way to check for a process exiting without spinning?
I don't know if it's useful for you, but CONFIG_CONNECTOR and CONFIG_PROC_EVENTS
will report process
On 7/30/07, Joseph Pingenot <[EMAIL PROTECTED]> wrote:
> What's the way to check for a process exiting without spinning?
I think you can get it from the taskstats interface, though I haven't
tried it. See Documentation/accounting/ for details.
Ray
-
To unsubscribe from this list: send the line
On 7/30/07, Joseph Pingenot [EMAIL PROTECTED] wrote:
What's the way to check for a process exiting without spinning?
I think you can get it from the taskstats interface, though I haven't
tried it. See Documentation/accounting/ for details.
Ray
-
To unsubscribe from this list: send the line
El Mon, 30 Jul 2007 22:25:21 -0500, Joseph Pingenot [EMAIL PROTECTED]
escribió:
More background, please?
What's the way to check for a process exiting without spinning?
I don't know if it's useful for you, but CONFIG_CONNECTOR and CONFIG_PROC_EVENTS
will report process
On Tue, 31 Jul 2007 20:31:49 +0200 Diego Calleja [EMAIL PROTECTED] wrote:
El Mon, 30 Jul 2007 22:25:21 -0500, Joseph Pingenot [EMAIL PROTECTED]
escribió:
More background, please?
What's the way to check for a process exiting without spinning?
I don't know if it's useful for you,
for most common usage scenarios, although will suspect that it
won't for for processes owned by another user (at least, I hope
it wouldn't).
What is dangerous about inotify on a proc file?
And if it's dangerous, should the inotify system call fail when trying to
set the watch? Bailout
Joseph Pingenot wrote:
While we're on the subject, is there some way to receive notification
that some aspect of a process changes (in this case, stopping using
CPU, but not exiting).
For some internal stuff a while back I did a patch that allows any
process to register for status change
en it exits.
> >er... ptrace(2)?
>
> Should work for most common usage scenarios, although will suspect that it
> won't for for processes owned by another user (at least, I hope
> it wouldn't).
>
> What is dangerous about inotify on a proc file?
Playing with the lifetime
although will suspect that it
won't for for processes owned by another user (at least, I hope
it wouldn't).
What is dangerous about inotify on a proc file?
--
[EMAIL PROTECTED]///
"There is also an entire branch in the physical therapy field d
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> I'm trying to implement pwait. It blocks until a specified PID exits,
> and then it exits.
er... ptrace(2)?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
> From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
> >> >From Joseph Pingenot on Monday, 30 July, 2007:
> >> >From Al Viro on Tuesday, 31 July, 2007:
> >> >>On Mon, Jul 30,
>From Al Viro on Tuesday, 31 July, 2007:
>On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
>> >From Joseph Pingenot on Monday, 30 July, 2007:
>> >From Al Viro on Tuesday, 31 July, 2007:
>> >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>> >>> I was trying to use
On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
> >From Joseph Pingenot on Monday, 30 July, 2007:
> >From Al Viro on Tuesday, 31 July, 2007:
> >>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> >>> I was trying to use inotify to watch process changes (especially
On Mon, Jul 30, 2007 at 10:25:21PM -0500, Joseph Pingenot wrote:
> >From Al Viro on Tuesday, 31 July, 2007:
> >On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> >> I was trying to use inotify to watch process changes (especially process
> >> termination) by watching /proc/.
> >>
>From Joseph Pingenot on Monday, 30 July, 2007:
>From Al Viro on Tuesday, 31 July, 2007:
>>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>>> I was trying to use inotify to watch process changes (especially process
>>> termination) by watching /proc/.
>>> Sadly, although I
>From Al Viro on Tuesday, 31 July, 2007:
>On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
>> I was trying to use inotify to watch process changes (especially process
>> termination) by watching /proc/.
>> Sadly, although I could see something reading various files, nothing
>>
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
> I was trying to use inotify to watch process changes (especially process
> termination) by watching /proc/.
>
> Sadly, although I could see something reading various files, nothing
> was issued when the process I was watching
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/.
Sadly, although I could see something reading various files, nothing
was issued when the process I was watching exited and the directory
went away.
Is this intentional, or a bug?
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/pid.
Sadly, although I could see something reading various files, nothing
was issued when the process I was watching exited and the directory
went away.
Is this intentional, or a bug?
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/pid.
Sadly, although I could see something reading various files, nothing
was issued when the process I was watching
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/pid.
Sadly, although I could see something reading various files, nothing
was
On Mon, Jul 30, 2007 at 10:25:21PM -0500, Joseph Pingenot wrote:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/pid.
Sadly,
From Joseph Pingenot on Monday, 30 July, 2007:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch process changes (especially process
termination) by watching /proc/pid.
Sadly, although I could see
On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
From Joseph Pingenot on Monday, 30 July, 2007:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch process changes (especially process
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
From Joseph Pingenot on Monday, 30 July, 2007:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 09:16:16PM -0500, Joseph Pingenot wrote:
I was trying to use inotify to watch
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at 10:31:13PM -0500, Joseph Pingenot wrote:
From Joseph Pingenot on Monday, 30 July, 2007:
From Al Viro on Tuesday, 31 July, 2007:
On Mon, Jul 30, 2007 at
On Mon, Jul 30, 2007 at 10:40:59PM -0500, Joseph Pingenot wrote:
I'm trying to implement pwait. It blocks until a specified PID exits,
and then it exits.
er... ptrace(2)?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
that it
won't for for processes owned by another user (at least, I hope
it wouldn't).
What is dangerous about inotify on a proc file?
--
[EMAIL PROTECTED]///
There is also an entire branch in the physical therapy field dedicated
to the treatment of little-finger
work for most common usage scenarios, although will suspect that it
won't for for processes owned by another user (at least, I hope
it wouldn't).
What is dangerous about inotify on a proc file?
Playing with the lifetime rules, for starters...
-
To unsubscribe from this list: send the line
Joseph Pingenot wrote:
While we're on the subject, is there some way to receive notification
that some aspect of a process changes (in this case, stopping using
CPU, but not exiting).
For some internal stuff a while back I did a patch that allows any
process to register for status change
On Jun 22, 2007, at 18:51:10, C. Scott Ananian wrote:
Back to kernel-land: in an IPv6 only world, it might make sense to
export a /proc file compatible with the format of /etc/resolv.conf,
with one DNS server address per line. If glibc uses/used inotify
on /etc/resolv.conf, then symlinking
On Jun 22, 2007, at 18:51:10, C. Scott Ananian wrote:
Back to kernel-land: in an IPv6 only world, it might make sense to
export a /proc file compatible with the format of /etc/resolv.conf,
with one DNS server address per line. If glibc uses/used inotify
on /etc/resolv.conf, then symlinking
On Fri, Jun 22, 2007 at 06:51:10PM -0400, C. Scott Ananian wrote:
> No, clearly inotify on all files in /proc is not the right thing to
> do. But I'm writing support for "RDNSS in RA" -- IPv6 Router
> Advertisement messages can include a DNS server specification, which
> makes IPv6 completely
ant that in the first place. If we wanted
inotify on /proc, it should work on all files I guess, but that's
an immense amount of work.
No, clearly inotify on all files in /proc is not the right thing to
do. But I'm writing support for "RDNSS in RA" -- IPv6 Router
Advertisement messages c
inotify on /proc, it should work on all files I guess, but that's
an immense amount of work.
No, clearly inotify on all files in /proc is not the right thing to
do. But I'm writing support for RDNSS in RA -- IPv6 Router
Advertisement messages can include a DNS server specification, which
makes
On Fri, Jun 22, 2007 at 06:51:10PM -0400, C. Scott Ananian wrote:
No, clearly inotify on all files in /proc is not the right thing to
do. But I'm writing support for RDNSS in RA -- IPv6 Router
Advertisement messages can include a DNS server specification, which
makes IPv6 completely
eems to do what I want, but it takes
> a struct dentry * -- how can I get a dentry from a struct
> proc_dir_entry and increment its ref count to keep it around? Any
> help would be appreciated. Thanks!
It sounds a little fishy to want that in the first place. If we wanted
inotify on /pro
I'd like to make a read-only /proc file which supports inotify -- that
is, the kernel can send change notifications to userland via the
inotify mechanism. I've found fsnotify_modify() (in
include/linux/fsnotify.h) which seems to do what I want, but it takes
a struct dentry * -- how can I get a
want, but it takes
a struct dentry * -- how can I get a dentry from a struct
proc_dir_entry and increment its ref count to keep it around? Any
help would be appreciated. Thanks!
It sounds a little fishy to want that in the first place. If we wanted
inotify on /proc, it should work on all files I
Hi
Can inotify monitor /proc? I would like to catch process creation and
deletion events. My first attempts are not succesul.
--
Regards
Mariusz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
Hi
Can inotify monitor /proc? I would like to catch process creation and
deletion events. My first attempts are not succesul.
--
Regards
Mariusz
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
47 matches
Mail list logo
