Sponsored Content
Full Discussion: Nohup and background jobs
Top Forums Shell Programming and Scripting Nohup and background jobs Post 302699045 by Uinx_addic on Tuesday 11th of September 2012 04:18:17 AM
Old 09-11-2012
Reply

Hi,

Actually i tried with &. my job is getting killed at terminal logout
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

background jobs

Hi, i have a problem with turning a job into backgrund. When i enter this at the shell: spice -b darlington.cir -r output.raw > screenout.tmp & and then let me show the currently running jobs, i get the following output: + Suspended (tty output) spice -b darlington.cir -r output.raw >... (4 Replies)
Discussion started by: qsi
4 Replies

2. Programming

Background jobs

Hi there, I'm quite new to UNIX for programming. I have a script that does this: Shows on screen real-time results taken from phone calls and logs them in a file. However, when I start my script, I want my script to start logging in the file in the background, so I can continue working on... (1 Reply)
Discussion started by: Jeremiorama
1 Replies

3. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ... (1 Reply)
Discussion started by: GrepMe
1 Replies

4. UNIX for Advanced & Expert Users

Notification from Background jobs

Reposting, as it got lost during the database backup. :( Via a shell script a spawn 3 background jobs namely a, b & c. These will take different times to complete. I want to print a different message on completion of each. How can i find out when each one has completed independently. ... (19 Replies)
Discussion started by: vibhor_agarwali
19 Replies

5. UNIX for Dummies Questions & Answers

Background jobs

If I run a job in the background and logoff. Will the job continue to run or will my processes be killed ? (1 Reply)
Discussion started by: jxh461
1 Replies

6. UNIX for Advanced & Expert Users

nohup and background process

What is the difference between running a process using nohup and running a process in background ? Please explain (6 Replies)
Discussion started by: srksn
6 Replies

7. Solaris

solaris terminal sessions terminated and also nohup jobs

Admins, We have a strange problem on our solaris zones. We have four zones on a Global server (Sun-Fire-V890; Solaris 10 Update 6) and the SSH sessions to all four zones are terminated at a specific time (11:10 PM) every night. The SSH session to the global server is not terminated. Also, any... (1 Reply)
Discussion started by: yogijp
1 Replies

8. Programming

Background (nohup * &) SSH command block possible?

Hello, I am trying to find a way to send several sequential commands via SSH to a remote box in a single command. Thoughts so far: 1) Can I put them into a function and call the function within the ssh command? e.g. ssh <targetserver> $(functionx) No - then it calls the function in... (4 Replies)
Discussion started by: doonan_79
4 Replies

9. Shell Programming and Scripting

How to stop nohup which is working background

Please I have run a background script using nohup please tell me way to stop this. Thanks in Advance (4 Replies)
Discussion started by: mumakhij
4 Replies

10. UNIX for Dummies Questions & Answers

How do I send output of a background process to a file other than nohup.out?

I have a question. I will be running a background process using nohup and & command at end. I want to send output to a file say myprocess.out. So will this command work? nohup myprocess.ksh > myprocess.out & Thanks in advance guys !!! :) (3 Replies)
Discussion started by: vx04
3 Replies
LPRM(1) 						    BSD General Commands Manual 						   LPRM(1)

NAME
lprm -- remove jobs from the line printer spooling queue SYNOPSIS
lprm [-Pprinter] [-] [job # ...] [user ...] DESCRIPTION
The lprm utility will remove a job, or jobs, from a printer's spool queue. Since the spooling directory is protected from users, using lprm is normally the only method by which a user may remove a job. The owner of a job is determined by the user's login name and host name on the machine where the lpr(1) command was invoked. Options and arguments: -Pprinter Specify the queue associated with a specific printer (otherwise the default printer is used). - If a single '-' is given, lprm will remove all jobs which a user owns. If the super-user employs this flag, the spool queue will be emptied entirely. user Cause lprm to attempt to remove any jobs queued belonging to that user (or users). This form of invoking lprm is useful only to the super-user. job # A user may dequeue an individual job by specifying its job number. This number may be obtained from the lpq(1) program, e.g. % lpq -l 1st:ken [job #013ucbarpa] (standard input) 100 bytes % lprm 13 If neither arguments or options are given, lprm will delete the currently active job if it is owned by the user who invoked lprm. The lprm utility announces the names of any files it removes and is silent if there are no jobs in the queue which match the request list. The lprm utility will kill off an active daemon, if necessary, before removing any spooling files. If a daemon is killed, a new one is auto- matically restarted upon completion of file removals. ENVIRONMENT
If the following environment variable exists, it is utilized by lprm. PRINTER If the environment variable PRINTER exists, and a printer has not been specified with the -P option, the default printer is assumed from PRINTER. FILES
/etc/printcap Printer characteristics file. /var/spool/* Spooling directories. /var/spool/*/lock Lock file used to obtain the pid of the current daemon and the job number of the currently active job. DIAGNOSTICS
``Permission denied" if the user tries to remove files other than his own. SEE ALSO
lpq(1), lpr(1), lpd(8) HISTORY
The lprm command appeared in 3.0BSD. BUGS
Since there are race conditions possible in the update of the lock file, the currently active job may be incorrectly identified. BSD
June 6, 1993 BSD
All times are GMT -4. The time now is 01:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy