All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Guillaume <jean-guillaume.paradis@ericsson.ca>
To: linux-kernel@vger.kernel.org
Subject: ProcFs: FORCING  remove_proc_entry even if the directory is used (busy)  ??
Date: Thu, 09 Oct 2003 13:21:19 -0400	[thread overview]
Message-ID: <3F85990F.6070902@ericsson.ca> (raw)

Hi all,

   I have a program that automaticaly recreate a directory in /proc, 
based on some events. To do this, I do a remove_proc_entry, and then 
recreate the directory.

   However, if someone is using a console and is currently IN my /proc 
directory, remove_proc_entry fails, saying that the dir is "busy".

   Any way to force the deletion? Or any ideas for workarounds?


   Many thanks

      Jena-Guillaume

             reply	other threads:[~2003-10-09 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 17:21 Jean-Guillaume [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-29 17:40 Simple Procfs question: Triggering an "action" when opening a directory instead of a file (with seqfile.h)??? Jean-Guillaume
2003-10-09 15:27 ` ProcFs: FORCING remove_proc_entry even if the directory is used (busy) ?? Jean-Guillaume

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F85990F.6070902@ericsson.ca \
    --to=jean-guillaume.paradis@ericsson.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.