I have an situation that are quite strange to me. I am not able to exit the server terminal and enter back into my home computer terminal by the command
like I used to be able to exit the server terminal with before. I end up into my root shell again without even typing the root password like I usually type
for accessing the root shell after having confirmed the root password.
I just checked to find out how the terminal were replying for adding and example for the situation but the situation seemed to be different while I now tried again. I guess I am not in the need of an solution right away other than to the experience of not understanding the situation that now seem to be solved.
Hi,
Can someone please help me in resolving this issue -
I am doing SSH from a server 1 to another server 2 and executing some statements there and then automatically exit out of second server to the first where script was getting executed.
Can you please help me script this code ?
Thanks (3 Replies)
I have had a look around and can not find the answer, I dont think im searching for the right phrase.
I have written a script to control common functions on my server, however when exiting the script the terminal starts directly below the script that was running... how can i clear this so it... (2 Replies)
hi
while executing the following script, my terminal window is getting closed if I enter a invalid option. I want the script should go back the the command prompt. how to do achive it. i execute the script as . ./test
#! /usr/bin/ksh
Printf " Type of Installer : \n\t\t 1. Whole Build... (3 Replies)
Not really a newbie, but I have a strange problem and I'm not sure how to further troubleshoot it.
I have to log out of a virtual terminal by typing exit, then exit again as in:
woodnt@toshiba-laptop ~ $ exit
logout
woodnt@toshiba-laptop ~ $ exit
logout
I DON'T have to do this when I'm... (1 Reply)
hi,
I am using the below line to run a script from remote server(say server A) to another server(say server B).
ssh username@servername ksh script name.
The issue is the script logs into server B, executes the script on server B, transfers the file to server A but does not exit from... (4 Replies)
Well. I was recently given access to my work's machine via SSH. I'm pretty sure it's a SUSE machine, uname -a gives
Linux machinename 2.6.16.60-0.54.5-bigsmp #1 SMP Fri Sep 4 01:28:03 UTC 2009 i686 i686 i386 GNU/Linux
I'm not doing anything all that exciting, mostly data entry stuff.
We... (14 Replies)
Hi,
I am on unix serverA where i have a script called A.sh
more A.sh
echo "Hello"
ssh user1@serverB
echo "Welcome"
After the ssh takes me to serverB; i execute a script on serverB called B.sh
more B.sh
echo " You are serverB"
exit
exit
With the two exit statements on serverB... (7 Replies)
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Hello,
I am running a bash script to do an rsync back on a computer running MacOS High Sierra. This is the script I am using,
#!/bin/bash
# main backup location, trailing slash included
backup_loc="/Volumes/Archive_Volume/00_macos_backup/"
# generic backup function
function backup {... (12 Replies)
Discussion started by: LMHmedchem
12 Replies
LEARN ABOUT NETBSD
nohup
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