10 More Discussions You Might Find Interesting
1. Programming
Experts,
Need your help for this. Please support
My motive is to create seperate output file for each Input Files(File 1 and File2) in another folder say(/tmp/finaloutput)
Input files
File 1(1.1.1.1.csv)
a,b,c
43,17104773,3
45,17104234,4
File 2(2.2.2.2.csv)
a,b,c
43,17104773,1... (2 Replies)
Discussion started by: as7951
2 Replies
2. Debian
May somebody can give me a hint. I am still using my old squeeze and it works the way I want. But my recent post about changing the owners rights, e.g. 777 or 755 anyway, it could be 644 as well. While configuring a new pc, just by chance I discovered how to enter the BIOS. And here it comes. I... (11 Replies)
Discussion started by: 1in10
11 Replies
3. Shell Programming and Scripting
is it possible to change the inode value/ file path of a hard link? (2 Replies)
Discussion started by: fhill2
2 Replies
4. Shell Programming and Scripting
Dear All,
I have a template xml file like below.
....Some---Header.......
<SignalPreference>
...
<SignalName>STRING</SignalName>
...
</SignalPreference>
......Some formatting text.......
<SignalPreference>
.........
... (3 Replies)
Discussion started by: ks_reddy
3 Replies
5. Shell Programming and Scripting
Dear Members,
I have a table in Oracle DB and one of its column name is INFO which has data in text format which we need to fetch in a script and create an xml file of a new table from the input.
The contents of a single cell of INFO column is like:
Area:app - aam
Clean Up Criteria:... (0 Replies)
Discussion started by: Yoodit
0 Replies
6. Shell Programming and Scripting
Hi,
I am quite new to Perl scripting and i need to create a .TXT file using perl, with fields (A,B,C,D,E), and this text file should be named with current file creation date "XYZ_CCYYMMDD.TXT" (i.e.XYZ_2011042514:33 PM).
Can anyone who has done this, please share their expertise on this... (5 Replies)
Discussion started by: msrahman
5 Replies
7. UNIX for Dummies Questions & Answers
i am new to UNIX environment
please tell me how to identify a link whether it is a Hardlink or Softlink ?
what is the command?
thank you all .......:o:o (2 Replies)
Discussion started by: sasith90
2 Replies
8. UNIX for Dummies Questions & Answers
unix program to which a directory name will be passed as
parameter. This directory will contain files with various
extensions. This script will create directories with the names of the
extention of the files and then put the files in the
corresponding folder. All files which do not have any... (2 Replies)
Discussion started by: Deekay.p
2 Replies
9. Filesystems, Disks and Memory
At risk of twisting the rules to nearly the point of breaking (if you think this goes too far mods, I apologise and accept that this should be deleted), I'm hoping someone might be able to cast a little light on the following problem regarding hard links to files.
... (6 Replies)
Discussion started by: Smiling Dragon
6 Replies
10. AIX
I have to move a lpar from one 671 to another (aix 5.2 ML 07)
when I run mksysb, It alway hangs with "archieving file list"
I've tried to exlude every directory, but still not working
the only thing that can be a problem, is a hardlink directory
normally it should not be possible to... (4 Replies)
Discussion started by: funksen
4 Replies
ARCHIVE_ENTRY_LINKIFY(3) BSD Library Functions Manual ARCHIVE_ENTRY_LINKIFY(3)
NAME
archive_entry_linkresolver, archive_entry_linkresolver_new, archive_entry_linkresolver_set_strategy, archive_entry_linkresolver_free,
archive_entry_linkify -- hardlink resolver functions
LIBRARY
Streaming Archive Library (libarchive, -larchive)
SYNOPSIS
#include <archive_entry.h>
struct archive_entry_linkresolver *
archive_entry_linkresolver_new(void);
void
archive_entry_linkresolver_set_strategy(struct archive_entry_linkresolver *resolver, int format);
void
archive_entry_linkresolver_free(struct archive_entry_linkresolver *resolver);
void
archive_entry_linkify(struct archive_entry_linkresolver *resolver, struct archive_entry **entry, struct archive_entry **sparse);
DESCRIPTION
Programs that want to create archives have to deal with hardlinks. Hardlinks are handled in different ways by the archive formats. The
basic strategies are:
1. Ignore hardlinks and store the body for each reference (old cpio, zip).
2. Store the body the first time an inode is seen (ustar, pax).
3. Store the body the last time an inode is seen (new cpio).
The archive_entry_linkresolver functions help by providing a unified interface and handling the complexity behind the scene.
The archive_entry_linkresolver functions assume that archive_entry instances have valid nlinks, inode and device values. The inode and
device value is used to match entries. The nlinks value is used to determined if all references have been found and if the internal refer-
ences can be recycled.
The archive_entry_linkresolver_new() function allocates a new link resolver. The instance can be freed using
archive_entry_linkresolver_free(). All deferred entries are flushed and the internal storage is freed.
The archive_entry_linkresolver_set_strategy() function selects the optimal hardlink strategy for the given format. The format code can be
obtained from archive_format(3). The function can be called more than once, but it is recommended to flush all deferred entries first.
The archive_entry_linkify() function is the core of archive_entry_linkresolver. The entry() argument points to the archive_entry that should
be written. Depending on the strategy one of the following actions is taken:
1. For the simple archive formats *entry is left unmodified and *sparse is set to NULL.
2. For tar like archive formats, *sparse is set to NULL. If *entry is NULL, no action is taken. If the hardlink count of *entry is larger
than 1 and the file type is a regular file or symbolic link, the internal list is searched for a matching inode. If such an inode is
found, the link count is decremented and the file size of *entry is set to 0 to notify that no body should be written. If no such inode
is found, a copy of the entry is added to the internal cache with a link count reduced by one.
3. For new cpio like archive formats a value for *entry of NULL is used to flush deferred entries. In that case *entry is set to an arbi-
trary deferred entry and the entry itself is removed from the internal list. If the internal list is empty, *entry is set to NULL. In
either case, *sparse is set to NULL and the function returns. If the hardlink count of *entry is one or the file type is a directory or
device, *sparse is set to NULL and no further action is taken. Otherwise, the internal list is searched for a matching inode. If such
an inode is not found, the entry is added to the internal list, both *entry and *sparse are set to NULL and the function returns. If
such an inode is found, the link count is decremented. If it remains larger than one, the existing entry on the internal list is
swapped with *entry after retaining the link count. The existing entry is returned in *entry. If the link count reached one, the new
entry is also removed from the internal list and returned in *sparse. Otherwise *sparse is set to NULL.
The general usage is therefore:
1. For each new archive entry, call archive_entry_linkify().
2. Keep in mind that the entries returned may have a size of 0 now.
3. If *entry is not NULL, archive it.
4. If *sparse is not NULL, archive it.
5. After all entries have been written to disk, call archive_entry_linkify() with *entry set to NULL and archive the returned entry as long
as it is not NULL.
RETURN VALUES
archive_entry_linkresolver_new() returns NULL on malloc(3) failures.
SEE ALSO
archive_entry(3)
BSD
February 2, 2012 BSD