Sponsored Content
Full Discussion: 0 byte file with no name????
Top Forums Shell Programming and Scripting 0 byte file with no name???? Post 302132513 by miltonkeynesguy on Friday 17th of August 2007 08:01:47 AM
Old 08-17-2007
I searched in google for deleting a file using inode...

I have managed to delete the file using the following...

by inode

#ls -i
#find . -inum 968746 -exec rm -i {} \;

Thanks for the idea Robotronic :-)
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to find if a file is zero byte or not?

hi, How to check if a file or files are of zero bytes and if yes, then to print their names? Ashu (1 Reply)
Discussion started by: er_ashu
1 Replies

2. Shell Programming and Scripting

Check if 2 files are identical byte-to-byte?

In my server migration requirement, I need to compare if one file on old server is exactly the same as the corresponding file on the new server. For diff and comm, the inputs need to be sorted. But I do not want to disturb the content of the file and need to find byte-to-byte match. Please... (4 Replies)
Discussion started by: krishmaths
4 Replies

3. UNIX for Dummies Questions & Answers

ftp 0 byte file

I have some clients uploading 0byte files to my ftp server unfortunately they dial in to an isp first so I'm not having any luck figuring out where they are coming from. I'm looking for a way to have the ftp server reject 0 byte files I checked man on vsftpd and did not see anything is there... (1 Reply)
Discussion started by: jjmill1979
1 Replies

4. Shell Programming and Scripting

Remove a byte(Last byte from the last line)

Hi All Can anyone please suggest me how to remove the last byte from a falt file .This is from the last line's last BYTE. Please suggest me something. Thank's and regards Vinay (1 Reply)
Discussion started by: vinayrao
1 Replies

5. Shell Programming and Scripting

delete zero byte file

Hello I have a requirement where i need to find the zero byte size file in the directory and need to delete that zero byte file. Thanks (2 Replies)
Discussion started by: dsdev_123
2 Replies

6. Shell Programming and Scripting

Need specific byte positions of a file

Hello , I need to extract data from specific byte positions of a file. I have tried the below command awk ' { printf "%s", substr($0, 642363,642369}' filename to extract data between byte positions 642363 and 642369 . However I did not get the expected result. I am new to awk... (6 Replies)
Discussion started by: rmv
6 Replies

7. Shell Programming and Scripting

Checking the file for non-zero byte

Hi, An 'If' clause has to be executed if file1.txt has any contents in it. Suggest us... (2 Replies)
Discussion started by: lavnayas
2 Replies

8. Shell Programming and Scripting

Perl- Output file is always 0 byte

Hi all, I am new to perl programming. However i have a script that connects to the database and spools that into an output file. Strange thing is that sometimes this script works and sometimes the ouput spool file is always 0 byte. I have verified the sql query and the query always returns... (5 Replies)
Discussion started by: amit1_x
5 Replies

9. Shell Programming and Scripting

Get Compressed byte offset from .gz file

Hi , I have a .gz file whose contents look like below. data1^filename1 data2^filename2. .. . . Is it possible to find out the byte offset of each record from the .gz file. Like in an uncompressed file. grep -nb "Filename" give the byte offset of the record in this case. ... (4 Replies)
Discussion started by: chetan.c
4 Replies

10. UNIX for Beginners Questions & Answers

Logrotate 0 byte file

Hello, For various reasons I decided to rebuild my log server on a new microSD. To simplify matters I restored a backed up copy of the appropriate config files and uploaded them to the new log server once syslog-ng was setup. The issue I am running into now is when logrotate compresses the log... (3 Replies)
Discussion started by: MyUserName7000
3 Replies
HISTORY(5)							File Formats Manual							HISTORY(5)

NAME
history - record of current and recently expired Usenet articles DESCRIPTION
The file <pathdb in inn.conf>/history keeps a record of all articles currently stored in the news system, as well as those that have been received but since expired. In a typical production environment, this file will be many megabytes. The file consists of text lines. Each line corresponds to one article. The file is normally kept sorted in the order in which articles are received, although this is not a requirement. Innd(8) appends a new line each time it files an article, and expire(8) builds a new version of the file by removing old articles and purging old entries. Each line consists of two or three fields separated by a tab, shown below as : [Hash] date [Hash] date token The Hash field is the ASCII representation of the hash of the Message-ID header. This is directly used for the key of the dbz(3). The date field consists of three sub-fields separated by a tilde. All sub-fields are the text representation of the number of seconds since the epoch -- i.e., a time_t; see gettimeofday(2). The first sub-field is the article's arrival date. If copies of the article are still present then the second sub-field is either the value of the article's Expires header, or a hyphen if no expiration date was speci- fied. If an article has been expired then the second sub-field will be a hyphen. The third sub-field is the value of the article's Date header, recording when the article was posted. The token field is a token of the article. This field is empty if the article has been expired. For example, an article whose Message-ID was <7q2saq$sal$1@isrv4.pa.vix.com>, posted on 26 Aug 1999 08:02:34 GMT and recieved at 26 Aug 1999 08:06:54 GMT, could have a history line (broken into three lines for display) like the following: [E6184A5BC2898A35A3140B149DE91D5C] 935678987~-~935678821 @030154574F00000000000007CE3B000004BA@ In addition to the text file, there is a dbz(3) database associated with the file that uses the Message-ID field as a key to determine the offset in the text file where the associated line begins. For historical reasons, the key includes the trailing byte (which is not stored in the text file). HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 3782, dated 2000-08-17. SEE ALSO
dbz(3), expire(8), inn.conf(5), innd(8), makehistory(8). HISTORY(5)
All times are GMT -4. The time now is 11:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy