[prev in list] [next in list] [prev in thread] [next in thread] 

List:       plug-mail
Subject:    Fwd: [PLUG] Weird Inode values
From:       "Ashutosh Adkar" <ashu.adkar () gmail ! com>
Date:       2007-01-22 16:02:01
Message-ID: 51e0025b0701220750g9fed0f4jdc09a1b9853745c2 () mail ! gmail ! com
[Download RAW message or body]

---------- Forwarded message ----------
From: K. Shantanu <linux@shantanukulkarni.org>
Date: Jan 22, 2007 9:12 PM
Subject: Re: [PLUG] Weird Inode values
To: Pune GNU/Linux Users Group Mailing List <plug-mail@plug.org.in>

* Ashutosh Adkar <ashu.adkar@gmail.com> [070121 17:38]:
> >How are you modifying the file? With text editor I believe.
> >
>
> vi of course.But what the heck.Even a 'touch' command changes the inode
> >value

I think you are getting confused. "touch" does not change inode number,
it changes inode data essentially modification and access time date
stamps by default. vi (like some editors and some other utilities),
makes a copy of the current file and then removes the file when the
user saves the file, the copy is "re-saved" to the original position and
hence the inode is changed. If you want to cross check, make a hard link
to the file and then edit the file using vi and you will find the inode
will not be changed.

Shantanu
www.shantanukulkarni.org
--
No.I know 'touch' shouldn't change the inode value.Thats what the whole
issue is.I do a 'touch' on a particular file and then if I use 'stat' I see
a different inode value.
--
______________________________________________________________________
Pune GNU/Linux Users Group Mailing List:      (plug-mail@plug.org.in)
List Information:  http://plug.org.in/cgi-bin/mailman/listinfo/plug-mail
Send 'help' to plug-mail-request@plug.org.in for mailing instructions.
--
______________________________________________________________________
Pune GNU/Linux Users Group Mailing List:      (plug-mail@plug.org.in)
List Information:  http://plug.org.in/cgi-bin/mailman/listinfo/plug-mail
Send 'help' to plug-mail-request@plug.org.in for mailing instructions.
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic