Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #161
Difficulty: Easy
Application programmers are typically concerned only with interfaces in the application layer and often also in the transport layer, while the layers below are services provided by the TCP/IP stack in the operating system.
True or False?
Linux & Unix Commands - Search Man Pages

iput(9) [centos man page]

IPUT(9) 							   The Linux VFS							   IPUT(9)

NAME
iput - put an inode SYNOPSIS
void iput(struct inode * inode); ARGUMENTS
inode inode to put DESCRIPTION
Puts an inode, dropping its usage count. If the inode use count hits zero, the inode is then freed and may also be destroyed. Consequently, iput can sleep. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 IPUT(9)

Check Out this Related Man Page

CLRI(8) 						    BSD System Manager's Manual 						   CLRI(8)

NAME
clri -- clear an inode SYNOPSIS
clri special_device inode_number ... DESCRIPTION
Clri is obsoleted for normal file system repair work by fsck(8). Clri zeros out the inodes with the specified inode number(s) on the filesystem residing on the given special_device. The fsck(8) utility is usually run after clri to reclaim the zero'ed inode(s) and the blocks previously claimed by those inode(s). Both read and write permission are required on the specified special_device. The primary purpose of this routine is to remove a file which for some reason is not being properly handled by fsck(8). Once removed, it is anticipated that fsck(8) will be able to clean up the resulting mess. SEE ALSO
fsck(8), fsdb(8), icheck(8), ncheck(8) BUGS
If the file is open, the work of clri will be lost when the inode is written back to disk from the inode cache. 4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution

Featured Tech Videos