Sponsored Content
Top Forums UNIX for Advanced & Expert Users GNU tar automatic gz detection/decompression Post 302255595 by Annihilannic on Thursday 6th of November 2008 07:25:54 PM
Old 11-06-2008
Thanks for satisfying my curiosity. I'm still using my SuSE 6.0 installation from about '95 (with manual updates to 2.6 kernel, etc), so some of the utilities are showing their age!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

gnu tar on Solaris 8

Here is how I got where I am: I tried untarring tomcat and at the end of the untar I get the following: So I downloaded GNU tar and did a pkgadd -d, which installed the package. But when I run /usr/local/bin/tar, I get this message: (1 Reply)
Discussion started by: dangral
1 Replies

2. Solaris

GNU tar on SUN 9

I downloaded GNUtar from sunfreeware.con and installed it on a sparc running sun 9. Performed pkgadd -d on the required lib and tar file and everything seemed to be ok. I tried to extract a file from a tar created using the sun version with no success. Tar ran for several hours working on the... (6 Replies)
Discussion started by: thumper
6 Replies

3. UNIX for Dummies Questions & Answers

automatic tar xf of file with unknown name

Hi all, With curl I can fetch a tar archive from a web server which contains a file ending with .scf which I am interested in. Unfortunately the file name may vary and the subdirectory inside the tar archive may change. I can manually browse the directory structure and extract the file and then... (3 Replies)
Discussion started by: tkrahn
3 Replies

4. Programming

Parallel Processing Detection and Program Return Value Detection

Hey, for the purpose of a research project I need to know if a specific type of parallel processing is being utilized by any user-run programs. Is there a way to detect whether a program either returns a value to another program at the end of execution, or just utilizes any form of parallel... (4 Replies)
Discussion started by: azar.zorn
4 Replies

5. Emergency UNIX and Linux Support

extraction of directory and below using gnu tar

i need to restore everything in a certain directory and lower. I have a tgz archive of all of the files, and i need to restore everything in /user/home/xxxx/ and below. this is a users home directory. this is a dumb question and i know when i see the answer i am going to say DUH, but i am... (2 Replies)
Discussion started by: frankkahle
2 Replies

6. Solaris

ZCAT xxx.Z|tar -xvf - decompression slow ?

I have recently built a new server and patched Soalris 10 up tp latest bundle etc... When I run a decompress using the format zcat fred.Z |tar -xvf - it runs at a very slow rate. A similiar server which is less powerful runs over twice as quick. Is there any work arounds to configure decompress... (4 Replies)
Discussion started by: smcart
4 Replies

7. OS X (Apple)

Semi-Automatic Arduino Detection.

I am working on a semi-auto detection idea for Arduino for the Scope project. It does require a little user intervention but minimal. It works by just responding to two on screen prompts to unplug and plug Arduino into a USB port. There are two versions and both work perfectly well and give... (3 Replies)
Discussion started by: wisecracker
3 Replies

8. AIX

GNU TAR vs NATIVE AIX TAR

Hello, Getting this very strange error, made tar/zip through gnu tar GNU Tar ( successful tar and zip without any errors ) /opt/freeware/bin/tar cvf - /oraapp| gzip > /backup/bkp_15_6_16_oraapp.tgz GNU unTar error root@test8:/>gunzip < /config1/bkp_15_6_16_oraapp.tgz |... (5 Replies)
Discussion started by: filosophizer
5 Replies
expanded_node_host_names(5)					File Formats Manual				       expanded_node_host_names(5)

NAME
expanded_node_host_names - enable maximum length expansion of the system node and host names VALUES
Failsafe Default Allowed Values DESCRIPTION
The tunable controls the length of the system node and host names. When this tunable value is 0, the system utilities used to set node and host names allow compatible name lengths. That is, 8 and 64 bytes for node and host name, respectively. When this tunable value is 1, the utilities allow expanded lengths up to 255 bytes. Changing this tunable does not affect the current system node and host names. Node and host names larger than 8 and 64 bytes, respectively, can cause anomalous or incorrect behavior in applications using these names. See the WARNINGS section for more information. Who Is Expected to Change This Tunable? The system administrator may change this tunable when it is necessary to change the maximum allowed length of the system node and/or host names. Restrictions on Changing This tunable is dynamic. Changing its value to 1 immediately allows the administrator to assign expanded (up to 255 bytes) node or host names. Changing its value to 0 enforces the compatible maximum of 8 and 64 byte node and host names on any subsequent name setting but does not affect the current name settings. When Should the Value of This Tunable Be Raised? This tunable may be raised to 1 when it is necessary to assign an expanded node and/or host name. What are the Side Effects of Raising the Value? Raising the tunable value to 1 causes the system utilities used to set node and host names to allow names up to 255 bytes. When Should the Value of This Tunable Be Lowered? This tunable should be lowered to 0 when it is determined that expanded node and host names are not necessary. What are the Side Effects of Lowering the Value? Lowering the tunable value to 0 causes the system utilities used to set node and host names to allow names up to 8 and 64 bytes, respec- tively. What Other Tunable Values Should Be Changed at the Same Time? None. APPLICATION USAGE
For more information on usage see the whitepaper WARNINGS
Node and host names in excess of 8 and 64 bytes, respectively, can cause anomalous behavior or failure in applications using these names. The administrator should read and understand the issues as described in the related documentation (see the whitepaper and nodehostname- size(5)). Warnings are always issued from the tunable handler when this tunable is changed. When this tunable value is 0 (off), the system interfaces and commands which set node and host names quietly truncate inputs to 8 or 64 bytes, respectively. This behavior is consistent with previous versions. There is no error nor warning provided. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. AUTHOR
was developed by HP. SEE ALSO
hostname(1), uname(1), setuname(1M), gethostname(2), sethostname(2), uname(2), hostname(5), nodehostnamesize(5). whitepaper, available on Tunable Kernel Parameters expanded_node_host_names(5)
All times are GMT -4. The time now is 10:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy