Sponsored Content
Full Discussion: nohup - help!
Top Forums UNIX for Dummies Questions & Answers nohup - help! Post 302140333 by bluemoon1 on Thursday 11th of October 2007 11:49:01 PM
Old 10-12-2007
I didn't use the no-interactive (-n) option because I wanted to capture the output & save them in a log file so we know if anything /file failed to get installed.
I do however suppress the interaction by using "-a" & and my own pkgadm file to overwrite the system default under /var/sadm/install/admin on my solaris.

Thank you so much for answering that question- the other pkg must be opening dev/tty explicitly - & yet, it indeed was asking for pwds.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Nohup

Hi, Using nohup it sends output automatically to $HOME/nohup.out - how do I direct this output to another named file instead, so I can run several scripts in the background at once, directing their outputs into individual log files? Cheers (3 Replies)
Discussion started by: miwinter
3 Replies

2. UNIX for Advanced & Expert Users

Help on nohup

Hi I submitted a long running executable without using nohup. Now, is there any way I can assure to keep that process ON even if my session gets killed? Thanks Bobby (3 Replies)
Discussion started by: bobbyjohnz
3 Replies

3. Solaris

NOHUP not working

Hello All, Here is a problem of NOHUP. I am trying to run a process which needs to be up and running even if the session is closed. I tried running it with "nohup", but starngely it is not working, when i exit from the session the process is also getting killed? plz help me in finding out... (4 Replies)
Discussion started by: shivamasam
4 Replies

4. AIX

nohup.out

I have a program which writes to nohup.out ... over the time this nohup.out becomes a large file and i cannot read the contents of this file using a vi editor.... whe i do a vi nohup.out it gives an error insufficient memory.... do i need to clean this nohup.out periodically ( or compress it... (5 Replies)
Discussion started by: ramky79
5 Replies

5. Shell Programming and Scripting

Problem with nohup

Hello I am running this script inst.sh #!/bin/ksh sqlplus -s username/password @temp.sql ----Here is my temp.sql set serveroutput on select instance_name from V$instance; exit When i run the script inst.sh on the command prompt...it runs fine...but when i run it using... (5 Replies)
Discussion started by: njafri
5 Replies

6. UNIX for Dummies Questions & Answers

When we need nohup

Hi, I've read the man page on nohup. But I still can't see what's the differences if we just send a process to background versus sending a nohup process to background. eg: myprocess & vs nohup myprocess & Without nohup, myprocess would still run uninterruptible at background... (2 Replies)
Discussion started by: ehchn1
2 Replies

7. UNIX for Dummies Questions & Answers

nohup

Hi, We are trying to run a shell script using nohup command. But this scripts asks for user input (username and password). Once we enter credentials it should continue run in background. Can someone please suggest how can we implement this? we can't modify .sh file since they are provided by... (5 Replies)
Discussion started by: blak
5 Replies

8. UNIX for Dummies Questions & Answers

Nohup

Hi Every one , i wrote a script for nohpu ,which checks the service by using the port number and starts if it doesnt hear the port. It works good untill i colse the session. how to make it work even after closing the session .And aslo how to deamoize this script #!/bin/bash netstat -ptlen |... (2 Replies)
Discussion started by: vikatakavi
2 Replies

9. Shell Programming and Scripting

Saving nohup output to a file other than nohup.out

Shell : bash OS : Oracle Linux 6.4 I want to save the ouput of a nohup command to file other than nohup.out . Below are my 3 attempts. For both Attempt1 and Attempt2 , the redirection logs the output correctly to the output file. But I get the error "ignoring input and redirecting stderr to... (7 Replies)
Discussion started by: kraljic
7 Replies

10. Shell Programming and Scripting

Help with nohup

I have a script test1.ksh (Korn shell) and within that I am calling another script test2.ksh test2.ksh runs for a pretty long time and hence wanted to execute as nohup from within test1.ksh nohup ./test2.ksh Question 1) dont think the above is working , although executing the nohup... (1 Reply)
Discussion started by: alldbest
1 Replies
pkgrm(1M)																 pkgrm(1M)

NAME
pkgrm - remove a package from the system SYNOPSIS
pkgrm [-nv] [-a admin] [ [-A | -M] -R root_path] [-V fs_file] [pkginst... | -Y category[,category...]] pkgrm -s spool [pkginst... | -Y category[,category...]] pkgrm will remove a previously installed or partially installed package from the system. A check is made to determine if any other packages depend on the one being removed. If a dependency exists, the action taken is defined in the admin file. The default state for the command is in interactive mode, meaning that prompt messages are given during processing to allow the administra- tor to confirm the actions being taken. Non-interactive mode can be requested with the -n option. The -s option can be used to specify the directory from which spooled packages should be removed. Certain unbundled and third-party packages are no longer entirely compatible with the latest version of pkgrm. These packages require user interaction throughout the removal and not just at the very beginning. To remove these older packages (released prior to Solaris 2.4), set the following environment variable:NONABI_SCRIPTS=TRUE pkgrm permits keyboard interaction throughout the removal as long as this environment variable is set. The following options are supported: -a admin Use the installation administration file, admin, in place of the default admin file. pkgrm first looks in the current work- ing directory for the administration file. If the specified administration file is not in the current working directory, pkgrm looks in the /var/sadm/install/admin directory for the administration file. -A Remove the package files from the client's file system, absolutely. If a file is shared with other packages, the default behavior is to not remove the file from the client's file system. -M Instruct pkgrm not to use the $root_path/etc/vfstab file for determining the client's mount points. This option assumes the mount points are correct on the server and it behaves consistently with Solaris 2.5 and earlier releases. -n Non-interactive mode. If there is a need for interaction, the command will exit. Use of this option requires that at least one package instance be named upon invocation of the command. Certain conditions must exist for a package to be removed non-interactively or a non-restrictive admin file needs to be used. -R root_path Defines the full path name of a directory to use as the root_path. All files, including package system information files, are relocated to a directory tree starting in the specified root_path. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -s spool Remove the specified package(s) from the directory spool. The default directory for spooled packages is /var/sadm/pkg. -v Trace all of the scripts that get executed by pkgrm, located in the pkginst/install directory. This option is used for debugging the procedural and non-procedural scripts. -V fs_file Specify an alternative fs_file to map the client's file systems. Used in situations where the $root_path/etc/vfstab file is non-existent or unreliable. -Y category Remove packages based on the value of the CATEGORY parameter stored in the installed or spooled package's pkginfo(4) file. No package with the CATEGORY value of system can removed from the file system with this option. The following operand is supported: pkginst Specifies the package to be removed. The format pkginst.* can be used to remove all instances of a package. The asterisk character (*) is a special character to some shells and may need to be escaped. In the C-Shell, "*" must be surrounded by single quotes (') or preceded by a backslash (). Example 1: Removing All instances of SUNWjunk From client1 The following example removes all instances of SUNWjunk from client1: example% pkgrm -R /export/root/client1 SUNWjunk* Note the caveat on the use of the -R option in the description of that option, above. The following exit values are returned: 0 Successful completion. 1 Fatal error. 2 Warning. 3 Interruption. 4 Administration. 10 Reboot after removal of all packages. 20 Reboot after removal of this package. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), installf(1M), pkgadd(1M), pkgask(1M), pkgchk(1M), removef(1M), admin(4),pkginfo(4), attributes(5) 6 Apr 2005 pkgrm(1M)
All times are GMT -4. The time now is 11:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy