![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Inodes | nitin09 | Linux | 3 | 05-02-2008 07:12 AM |
| inodes | gfhgfnhhn | UNIX for Dummies Questions & Answers | 3 | 10-12-2006 02:12 AM |
| inodes | livemyway | SUN Solaris | 1 | 01-24-2006 05:45 AM |
| inodes??? | soliberus | SUN Solaris | 1 | 07-14-2005 09:46 AM |
| INodes... | boris888 | Filesystems, Disks and Memory | 3 | 05-09-2002 10:21 AM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Dear all,
We have a logfile which is written into by a background process running continuously. This logfile size keeps increasing rapidly. While trying to manipulate the file, we deleted the file from the directory. But the process kept on writing into the file and the directory space got filled up. According to inode concept, the file is not completely removed until the last reference to the inode is gone. My question is how to trace these inodes which exist even after the files get deleted but a process is working on it. Please let me know if i am not clear. |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|