linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux C Programming <linux-c-programming@vger.kernel.org>
Subject: Re: The stickybit!!
Date: Fri, 17 Dec 2004 10:34:02 +0100	[thread overview]
Message-ID: <20041217093402.GW16958@lug-owl.de> (raw)
In-Reply-To: <1103265276.6880.8.camel@myLinux>

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

On Fri, 2004-12-17 12:04:36 +0530, Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
wrote in message <1103265276.6880.8.camel@myLinux>:
> Hi,
> 	Though it is known that stickybit is obsolete, im just curious to see
> the effect of setting a sticky bit on an executable file.

It isn't obsolete. It's a rarely used feature that's actually quite
important. Most of the time, you can try to work around it, but the
sticky bit will most probably just stay as it is.

> 	Is there a way to findout the data if residing in swap area after the
> process is terminated, using a C program??

Not (easily), at last. You can try to open the swap area(s) with
O_DIRECT and prepare a copy of it. However, you don't know which pages
were owned by the terminated process formerly so you only can step
through all the bytes and hope to find something useful...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-12-17  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17  6:34 The stickybit!! Jagadeesh Bhaskar P
2004-12-17  9:34 ` Jan-Benedict Glaw [this message]
2004-12-17 10:38   ` Jagadeesh Bhaskar P
2004-12-17 15:20     ` Jan-Benedict Glaw
2004-12-18  0:25 ` Glynn Clements

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=20041217093402.GW16958@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).