07-19-2019
debugfs with its unlink and rm commands comes to mind, but it might suffer from the same problems as the other tools. When using it, be very careful and know exactly what you are doing!
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
when i try to ls -lrt the directory, the "undeletable" file is listed.
but when i try to ls -lrt *exe, the "undeletable" file is not listed.
this "undeletable" is the file that i want to delete from the directory.
but when i try to delete/rename/copy.... it, it show that "No such file or... (10 Replies)
Discussion started by: chxxangie
10 Replies
2. UNIX for Dummies Questions & Answers
I've some files created by a script.
For some reason last time the script run was interrupted for an error and the files produced by the script are undeletable.
i've tryed as root with command 'rm' and even if i got no error in command execution the files are still there.
These are the... (9 Replies)
Discussion started by: mirrorx
9 Replies
3. Shell Programming and Scripting
Hi Friends,
I'm a great fan of this forum... it has helped me tone my skills in shell scripting. I have a challenge here, which I'm sure you guys would help me in achieving...
File A has a list of job ids and I need to compare this with the File B (*.log) and File C (extend *.log) and copy... (6 Replies)
Discussion started by: asnandhakumar
6 Replies
4. Shell Programming and Scripting
Hi,
I need to compare 2 text files with around 60000 rows and 1 column. I need to compare these and write the mismatch data to 3rd file.
File1 - file2 = file3
wc -l file1.txt
58112
wc -l file2.txt
55260
head -5 file1.txt
101214200123
101214700300
101250030067
101214100500... (10 Replies)
Discussion started by: Divya Nochiyil
10 Replies
5. Shell Programming and Scripting
Shell script logic
Hi
I have 2 input files like with file 1 content as (file1)
"BRGTEST-242" a.txt "BRGTEST-240" a.txt "BRGTEST-219" e.txt
File 2 contents as fle(2)
"BRGTEST-244" a.txt "BRGTEST-244" b.txt "BRGTEST-231" c.txt "BRGTEST-231" d.txt "BRGTEST-221" e.txt
I want to get... (22 Replies)
Discussion started by: pottic
22 Replies
link(1) General Commands Manual link(1)
NAME
link, unlink - Creates an additional directory entry for an existing file
SYNOPSIS
link file1 file2
unlink file
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link: XCU5.0
unlink: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the
underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal
access rights to the underlying file.
The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory
entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link.
You should be familiar with the link() and unlink() system calls before you use these commands.
The link and unlink commands do not issue error messages when the associated system call is unsuccessful.
NOTES
The link and unlink commands cannot be used to link and unlink directories.
EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments
specified. The link() or unlink() system call failed.
SEE ALSO
Commands: fsck(8), ln(1)
Functions: link(2), unlink(2)
link(1)