10-26-2013
Quote:
Originally Posted by
Devyn
I know tar / cpio have limitations on 2GB, even on AIX 7.1, but what about other utilities?
The AIX
tar adheres to the USTAR standard, which in turn means: no single
input file processed by
tar can be larger than 8 GB, but the archive itself can be of (nearly) unlimited size. The reason for the limitation is the data structure of the USTAR header which can't hold size information of more than 8 GB.
I hope this helps.
bakunin
Last edited by bakunin; 10-26-2013 at 03:35 AM..
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Friends,
I have a file as below :
machine1:
abc
xyz
qwerty
machine2:
jkl
mno
machine3:
hhh
kkk
qwerty
Now ...i need to find all the stanza names that have the pattern "qwerty'"
in it...( i need to get the output as machine1 and machine3 since... (4 Replies)
Discussion started by: vijaya2006
4 Replies
2. Shell Programming and Scripting
Hi Friends,
I have a stanza file as below :
CuDv:
name = "hdisk34"
status = 0
chgstatus = 3
ddins = "scsidisk"
location = "06-08-02"
parent = "fscsi0"
connwhere = "W_0"
PdDvLn = "disk/fcp/mpioosdisk"
CuDv:
... (1 Reply)
Discussion started by: vijaya2006
1 Replies
3. HP-UX
Hi,
on HP-UX when I run command
ulimit -a
I get
time(seconds) 4096
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
Now I want to change
file(blocks) ... (2 Replies)
Discussion started by: namita.mundada
2 Replies
4. Shell Programming and Scripting
Hello friends,
I have a text file with lot of stanzas with each starting with "O-O-O.
Sample file :-
1. d4 Nf6 2. c4 g6 3. Nc3 d5 4. cxd5 Nxd5 5. e4 Nxc3 6. bxc3 Bg7 7. Nf3 c5 8.
Rb1 O-O 9. Be2 cxd4 10. cxd4 Qa5+ 11. Bd2 Qxa2 12. O-O Bg4 13. Bg5 h6 14. Be3 (8 Replies)
Discussion started by: prvnrk
8 Replies
5. Shell Programming and Scripting
As it was ultimately Don Craguns idea that saved the whole project i can as well give something back to the community. This is my stanza file parser, which was written only using ksh without any external programs.
The stanza structure
There is some inconsistency as to what exactly is meant by... (0 Replies)
Discussion started by: bakunin
0 Replies
LEARN ABOUT NETBSD
passwd.conf
PASSWD.CONF(5) BSD File Formats Manual PASSWD.CONF(5)
NAME
passwd.conf -- password encryption configuration file
SYNOPSIS
passwd.conf
DESCRIPTION
The /etc/passwd.conf file, consisting of ``stanzas'', describes the configuration of the password cipher used to encrypt local or YP pass-
words.
There are default, user and group specific stanzas. If no user or group stanza to a specific option is available, the default stanza is
used.
To differentiate between user and group stanzas, groups are prefixed with a single colon (':').
Some fields and their possible values that can appear in this file are:
localcipher The cipher to use for local passwords.
Possible values are: ``old'', ``newsalt,<rounds>'', ``md5'', ``sha1,<rounds>'', and ``blowfish,<rounds>''. For ``newsalt'' the
value of rounds is a 24-bit integer with a minimum of 7250 rounds. For ``sha1'' the value of rounds is a 32-bit integer, 0
means use the default of 24680. For ``blowfish'' the value can be between 4 and 31. It specifies the base 2 logarithm of the
number of rounds.
If not specified, the default value is ``old''.
ypcipher The cipher to use for YP passwords.
The possible values are the same as for localcipher.
If not specified, the default value is ``old''.
To retrieve information from this file use pw_getconf(3).
FILES
/etc/passwd.conf
EXAMPLES
Use SHA1 as the local cipher and old-style DES as the YP cipher. Use blowfish with 2^5 rounds for root:
default:
localcipher = sha1
ypcipher = old
root:
localcipher = blowfish,5
SEE ALSO
passwd(1), pwhash(1), pw_getconf(3), passwd(5)
HISTORY
The passwd.conf configuration file first appeared in NetBSD 1.6.
The default value of localcipher was set to ``sha1'' in /etc/passwd.conf starting from NetBSD 6.0.
BSD
December 3, 2010 BSD