11-19-2002
try this...
nohup ./agent.be &
Cheers!
Vishnu.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Backup Exec Agent won't start....
Question: Has anyone had any previous experience working with Backup exec for Unix? I'm running SCO Openserver 5.0.5 and Backup Exec agent Version 5.01 Revision 5.032 Basically, these are the commands I'm issueing and here is the output.
# cd etc
# cd... (1 Reply)
Discussion started by: PatMcCoy
1 Replies
2. UNIX for Advanced & Expert Users
Hello,
When launching a recently installed UNIX agent for my Veritas backup exec server I receive "getservbyname (grfs, tcp) failed!"
I have checked to make sure the service exists under port 6101 and its there. I also removed and recreated the service but still no go. :confused: :confused:... (2 Replies)
Discussion started by: George26
2 Replies
3. SCO
Hello All,
We have Veritas Backup Exec on a Windows 2003 OS and trying to setup the Ralus agent on SCO to perform regular backups of our Unixware system; but for some reason after "I believe" installing the agent on SCO; and launching it using the 'agent.be" command I receive a syntax error... (1 Reply)
Discussion started by: Yorgy
1 Replies
4. SCO
I have 3 SCO 5.0.5 machines. Two are running the /etc/bkupexec/agent.be just fine but the 3rd fails with a NRL initialization error. It can't seem to find the backup server in the /etc/hosts file.
The entry is in the /etc/hosts file.
The perms are set correctly on /etc /etc/bkupexec... (0 Replies)
Discussion started by: cnpaul
0 Replies
5. UNIX for Dummies Questions & Answers
anyone ?
i install and it just fail to startup. (0 Replies)
Discussion started by: kakabobo
0 Replies
6. AIX
Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :(
Agent:
OS: AIX 5.3
Hostname: DB-HN-SRV02
IP: 10.1.4.64
Backup server:
OS: Windows Server 2003
Hostname: backup-srv
IP: 10.1.5.51
I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies
7. BSD
Hi
I'd like to backup my freeBSD 7.0 using Backup Exec 12.0
Where to download the Backup Exec Agent for Linux/Unix? (4 Replies)
Discussion started by: ccc
4 Replies
8. UNIX for Advanced & Expert Users
Hi
we use backup exec to backup our linux servers... question is what if the linux server is corrupted (/root) and doesnt boot up .. how would the backup exec restore /root if the server cant even start?
woukld we have to restore to another server then boot into rescue mode and copy across... (0 Replies)
Discussion started by: halacil
0 Replies
9. UNIX for Advanced & Expert Users
Hi
we use backup exec to backup our linux servers. I wondered if its possible to restore root backup of one server into another server and then rename hotsnames etc..for clone purpose?
does this work? how can it be done? (0 Replies)
Discussion started by: halacil
0 Replies
NOHUP(1) BSD General Commands Manual NOHUP(1)
NAME
nohup -- invoke a command immune to hangups
SYNOPSIS
nohup utility [arg ...]
DESCRIPTION
The nohup command allows the specified utility to be protected from termination if the user should become logged out (for example, due to a
modem line or TCP/IP connection being dropped). To do this, nohup sets the SIGHUP signal(3) (``terminal line hangup'') to be ignored, then
executes utility along with any arguments.
If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory. If standard error is a
terminal, it is directed to the same place as the standard output. If the output file nohup.out cannot be created in the current directory,
nohup attempts to create the file in the user's home directory. If the file nohup.out cannot be created, either in the current directory or
the user's home directory, nohup will exit without invoking utility, with an exit value as described below.
ENVIRONMENT
The following variable is used by nohup.
HOME User's home directory.
EXIT STATUS
The nohup utility exits with one of the following values:
126 The utility was found but could not be invoked.
127 The utility could not be found or an error occurred in nohup.
Otherwise, the exit status of nohup will be that of utility.
SEE ALSO
signal(3)
STANDARDS
The nohup command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD
July 15, 2005 BSD