10-15-2012
Many thanks for writing a follow-up.
I am going to change the thread title to "[Solved]".
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Needing to perform a backup of one system to the tape unit on another system. Why, well because the local tape device is stuffed and I desparately need to have a backup completed successfully sooner rather than not at all.
My question is how do I set the below code to allow me to perform... (3 Replies)
Discussion started by: Cameron
3 Replies
2. UNIX for Advanced & Expert Users
I am trying to perform a remote tape backup from one SCO openserver to another remote SCO Openserver which happens to have a tape drive configured.
I have added entries into host.equiv and .rhosts on the tape drive server:
prodution_server root # This is equivalent to the hostname and... (1 Reply)
Discussion started by: cstovall
1 Replies
3. Shell Programming and Scripting
i have two main servers which are both hpux. the problem is that i only have single dat drive to use with my backup (using tar command). it always takes me alot of time to perform this activity since the backup can only be done one at a time. there are other hpux box with a dat drive attached on... (3 Replies)
Discussion started by: inquirer
3 Replies
4. Solaris
I am currently using tar to backup a server that has 9gb of data.
This is fine and works fine, as part of this I send the backup to a remote tape on a remote server using rsh..
This is not very secure though is it?
Whats the best idea here - is there another way I should do this to be more... (1 Reply)
Discussion started by: frustrated1
1 Replies
5. Solaris
Hi,
Someone knows hot to create a flash archive to a remote tape device?
Here is my try:
$flarcreate -n nereus -S -t lisdev:/dev/rmt/1n
WARNING: hash generation disabled when using tape (-t)
current filter settings
Creating the archive...
ERROR: Unable to work archive.
Regards (4 Replies)
Discussion started by: spacewalker
4 Replies
6. Solaris
Hello Everybody
I have two servers, name A & B. I need to take a backup of one directory(/girish) on serverA. But my tape drive is in serverB through tar command. But when I run the following command it doesn't take the backup. Could any one correct my command to take a backup
tar cvf - ... (0 Replies)
Discussion started by: girish.batra
0 Replies
7. Solaris
howdy experts,
i am using 2 server- Solaris 5.9
i have tape device attached with 1 of my solaris server. But others not.
# modinfo|grep tape
152 13d43e4 1333c 33 1 st (SCSI tape Driver 1.231)
now i want to Backup DATA file and System File in Tape Drive.
How do I take data and... (3 Replies)
Discussion started by: thepurple
3 Replies
8. Solaris
Hello all,
I'm trying to backup some files on a solaris 10 machine to the remote tape drive connected to another solaris 10 machine.
I have set up rsh to allow for password-less connection between the servers, but I'm not able to write to the tape with the command:
root@sdp4a>tar cvf... (1 Reply)
Discussion started by: kerrygold
1 Replies
9. UNIX for Dummies Questions & Answers
Hi all,
I've got two HP machines running HP-UX 11.31 and would like to remotely backup one server onto another server's tape unit using the cpio command.
The two servers use a secured communication channel, i.e ssh.
Kindly help,
Koketso (1 Reply)
Discussion started by: Koketso
1 Replies
10. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT NETBSD
pthread_attr
PTHREAD_ATTR(3) BSD Library Functions Manual PTHREAD_ATTR(3)
NAME
pthread_attr_init, pthread_attr_destroy -- thread attribute operations
LIBRARY
POSIX Threads Library (libpthread, -lpthread)
SYNOPSIS
#include <pthread.h>
int
pthread_attr_init(pthread_attr_t *attr);
int
pthread_attr_destroy(pthread_attr_t *attr);
DESCRIPTION
Thread attributes are used to specify parameters to pthread_create(). One attribute object can be used in multiple calls to
pthread_create(), with or without modifications between the calls. The pthread_attr_t type is an opaque representation of the thread
attributes; any access to the object other than via the described pthread_attr_*() functions may result in undefined behavior.
The pthread_attr_init() function initializes attr with the default thread attributes used in the implementation. Depending on the implemen-
tation, undefined behavior may follow if an uninitialized thread attribute object is used with some of the thread attribute functions. It is
therefore a good practice to always use pthread_attr_init(), even if this might be unnecessary. Undefined behavior may also follow if an
already initialized attr is used with pthread_attr_init().
When the attribute object is no longer needed, it should be destroyed by using pthread_attr_destroy(). The function has no effect on threads
that were created by using a given attribute object. A destroyed attr can be reinitialized using pthread_attr_init(), but all other actions
with the destroyed object are unspecified.
The following standard thread attribute functions are available:
Function Description
pthread_attr_getdetachstate(3) thread detach state
pthread_attr_getguardsize(3) thread guard size
pthread_attr_getinheritsched(3) inherit scheduler attribute
pthread_attr_getschedparam(3) thread scheduling parameter
pthread_attr_getschedpolicy(3) thread scheduling policy
pthread_attr_getscope(3) thread contention scope
pthread_attr_getstack(3) thread stack
pthread_attr_getstacksize(3) thread stack size
pthread_attr_getstackaddr(3) thread stack address
Each listed pthread_attr_get*() function contains a pthread_attr_set*() counterpart. In addition, the following NetBSD specific extensions
are available:
Function Description
pthread_attr_get_np(3) attributes of a running thread
pthread_attr_getname_np(3) descriptive name of an attribute
RETURN VALUES
If successful, these functions return 0. Otherwise, an error number is returned to indicate the error.
ERRORS
No errors are defined for pthread_attr_init() and pthread_attr_destroy().
SEE ALSO
pthread_create(3), pthread_join(3)
STANDARDS
Both pthread_attr_init() and pthread_attr_destroy() conform to IEEE Std 1003.1-2001 (``POSIX.1'').
BSD
July 9, 2010 BSD