I try to run a script as background job.
script:
#!/usr/bin/csh
/usr/bin/date +20%y-%m-%d > ~/datsql.txt
If I start it I got this output:
tac> ./datermitteln&
293
+ Stopped (SIGTTOU) ./datermitteln&
I insert the following line inside my script, but without any... (3 Replies)
Hiya,
Recently I've run a few scripts in the foreground, but have realised later they should of been better nohup'd and placed in the background. I understand how to change a foreground job into a background one, but how would put the job into the nohup state?
Thanks (1 Reply)
on gnome i open a terminal and run wget http://soommmething & in the background. because wget shows me downloading progress percentage and download speed continuously, I exit the gnome-terminal
after a while i want to see the download percentage but dont know how. my ps -u myname shows that... (3 Replies)
Hi
Is there any way to suspend cron job without ommitting crontab entries??
I have a no of entries in crontab, which runs daily.......... what if I want to suspend all process in cron one day . Is there any one line command for it ??
Please suggest
Rergards
Pankaj (4 Replies)
Guys,
We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem.
Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run.
... (2 Replies)
Hi,
Should the user jobs specified in crontab be running in background?
Cron daemon is already running in background. So I am not sure
whether should the jobs (output and error messages are redirected to file)
ran by it be explicitly stated to be run in background (& at end of command)
if one... (1 Reply)
Here is some back ground on the script. The script is to poll an arbitrary number of DB's. To do this I am creating a function that takes the file_path to the DB and the min poll interval as arguments. The function will be called for each DB and then ran in the background. The function I was... (6 Replies)
Hello everyone
While working on TUI for scripts, there there came the idea to' add a command' for dd too.
That was, after 'wrapping' tar and wget either, to display their growing size and return the exit code with a textual-visual-feedback to the user.
Now displaying the filesize of a... (13 Replies)
Discussion started by: sea
13 Replies
LEARN ABOUT OSF1
fg
fg(1) General Commands Manual fg(1)NAME
fg - Runs jobs in the foreground
SYNOPSIS
fg [job_id...]
Note
The C shell has a built-in version of the fg command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/fg. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
fg: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
None
OPERANDS
Specifies the job to be run as a foreground job. If no job_id operand is given, the job_id for the job that was most recently suspended,
placed in the background or run as a background job is used. The format of job_id is described in the Jobs section of the ksh(1) reference
page.
DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the fg utility moves a background job from the cur-
rent environment into the foreground.
Using fg to place a job into the foreground removes its process ID from the list of those "known in the current shell execution environ-
ment"; see the Jobs section of the ksh(1) reference page.
RESTRICTIONS
If job control is disabled, the fg utility exits with an error and no job is placed in the foreground. The fg utility does not work as
expected when it is operating in its own utility execution environment because that environment has no applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of fg: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the
processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), jobs(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)fg(1)