04-30-2008
How can I authorize a non-root user to do a system backup with 'mksysb'?
I use AIX 5.2 I want to allow a non-root user to do a system backup with 'mksysb' command.
I try to add 'ManageBackup' Role to that non-root user but it have an error "ksh: mksysb: 0403-006 Execute permission denied."
What should I do?
10 More Discussions You Might Find Interesting
1. AIX
Hi everyone,
I have no AIX experience at all. We have an IBM Server running AIX v.5.1. The server has a DDS-4 tape drive. I need to take complete system and user data backup.Should be able to restore the system and the user data in the event of system corruption or disaster. I was told that for... (5 Replies)
Discussion started by: Sezgin
5 Replies
2. AIX
How I can to obtain a full Backup of a AIX server with the command "mksysb"?? what is the correct form?
Thanks (1 Reply)
Discussion started by: granador
1 Replies
3. AIX
hi guys,
i just want to take my server's mksysb backup through dvd-rom.but am having the doubt that, while am taking the mksysb backup in image it shows 8GB. So can i confirm that it takes 2 dvds and after writing in 1st cd it will ask for 2nd cd??????
please help me out. (1 Reply)
Discussion started by: rrlog
1 Replies
4. AIX
Hi,
Can any one suggest me how to take the mksysb backup in CD (VCD/DVD). I have tried like #mkcd -d /dev/cd0, but its not working. (3 Replies)
Discussion started by: oprakash
3 Replies
5. AIX
hi
we are having one rootvg in that we created one lv named mksysb_backuplv
and normally script will run accordingly to take the backup in the cron,here i just want to know if any rootfilesystem was correpted like /usr or /tmp ,then how could i restore the particular filesystme from the... (1 Reply)
Discussion started by: senmak
1 Replies
6. AIX
Hi,
Currently we are taking mksysb backup through smitty mksysb command and directing the backup to happen on a tape.We have inbuilt tape drives in the AIX servers. Can we take the mksysb backup through 3rd party software tool (Symantec netbackup of IBm TSM). If yes what is the procedure and... (4 Replies)
Discussion started by: dwiravi
4 Replies
7. AIX
How to block the root user login in system direct console. Users should login with non-root ids themselves and then use the su command to become root. Which configuration file i need to check and disable it. (5 Replies)
Discussion started by: kmvinay
5 Replies
8. AIX
i have an AIX server and planning to upgrade the operating system, before that i want to take a system backup which can be used in case of upgrade failure. i dont have NIM server t hold the mksysb backups. so i have the only option of taking the backup on DVD. i have the following optical drive... (5 Replies)
Discussion started by: saikiran_1984
5 Replies
9. Shell Programming and Scripting
I am trying a cron on root user to backup to tape using TAR command
here is the cron entry
11 08 * * 6 /erdhot1cron 2>&1 >> /test3/scripts/dba/erdhot1cron.log
here is script inside - edhot1cron
#!/bin/bash
vsysdt=`date +%d%m%y`
date
tar -cvf /dev/st0... (4 Replies)
Discussion started by: vijaymec50
4 Replies
10. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
LEARN ABOUT NETBSD
fchroot
CHROOT(2) BSD System Calls Manual CHROOT(2)
NAME
chroot -- change root directory
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
chroot(const char *dirname);
int
fchroot(int fd);
DESCRIPTION
dirname is the address of the pathname of a directory, terminated by an ASCII NUL. chroot() causes dirname to become the root directory,
that is, the starting point for path searches of pathnames beginning with '/'.
In order for a directory to become the root directory a process must have execute (search) access for that directory.
If the current working directory is not at or under the new root directory, it is silently set to the new root directory. It should be noted
that, on most other systems, chroot() has no effect on the process's current directory.
This call is restricted to the super-user.
The fchroot() function performs the same operation on an open directory file known by the file descriptor fd.
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate an error.
ERRORS
chroot() will fail and the root directory will be unchanged if:
[ENOTDIR] A component of the path name is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded {NAME_MAX} characters, or an entire path name exceeded {PATH_MAX} characters.
[ENOENT] The named directory does not exist.
[EACCES] Search permission is denied for any component of the path name.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EFAULT] dirname points outside the process's allocated address space.
[EIO] An I/O error occurred while reading from or writing to the file system.
[EPERM] The effective user ID of the calling process is not the super-user.
fchroot() will fail and the root directory will be unchanged if:
[EACCES] Search permission is denied for the directory referenced by the file descriptor.
[EBADF] The argument fd is not a valid file descriptor.
[EIO] An I/O error occurred while reading from or writing to the file system.
[ENOTDIR] The argument fd does not reference a directory.
[EPERM] The effective user ID of the calling process is not the super-user.
SEE ALSO
chdir(2)
STANDARDS
The chroot() function conforms to X/Open System Interfaces and Headers Issue 5 (``XSH5''), with the restriction that the calling process'
working directory must be at or under the new root directory. Otherwise, the working directory is silently set to the new root directory;
this is an extension to the standard.
chroot() was declared a legacy interface, and subsequently removed in IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The chroot() function call appeared in 4.2BSD. Working directory handling was changed in NetBSD 1.4 to prevent one way a process could use a
second chroot() call to a different directory to "escape" from the restricted subtree. The fchroot() function appeared in NetBSD 1.4.
BSD
April 18, 2001 BSD