- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Tar trouble!
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2002 04:17 PM
01-26-2002 04:17 PM
Re: Tar trouble!
There is another circumstance under which the wildcard * will not work and that is when your argument list is too long. The OS has a limit to the number of arguments it can expand the wildcard to. If you exceed this limit, you will encounter the following error message:
"Argument list too long"
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2002 07:23 PM
01-26-2002 07:23 PM
Re: Tar trouble!
tar cvf - .|(cd /DESTINATION;tar xvfp -)
This reads the current directory (the dot to the left of the | (pipe) symbol) and writes the result to standard output (the - (dash)). To the right of the pipe, the cd command moves standard output to the destination directory, and the tar xvfp - command reads from standard input and writes to the current directory.
With this method, you will not have to create ANY file, but use standard input and output instead of a intermediary tar file.
A nifty aspect of this is the extreme speed at which the data is copied. I just used this very command a couple of hours ago to move Oracle's home directory from one disk drive to another, as the old drive was being replaced. Once the move was made, I demounted the old disk and mounted the new one in the same place. This also keeps ownership, permissions and timestamps intact, which is very important for Oracle files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2002 06:03 AM
01-31-2002 06:03 AM
Re: Tar trouble!
rm /home*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2002 06:30 AM
01-31-2002 06:30 AM
Re: Tar trouble!
How about...
cd /home
#If that messed up tar exist, remove it
files=`ls`
tar cvpf - `echo $files` | gzip > home.TAR.gz
That should resolve your problem.
...jcd...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2002 08:34 AM
01-31-2002 08:34 AM
Re: Tar trouble!
I assume you really want to move the /home filesystem to another computer, if so
on target m/c
remsh
If you just want home.tar (a tar of /home) on another computer try
on target m/c
remsh
Tim
- « Previous
-
- 1
- 2
- Next »