Sponsored Content
Top Forums UNIX for Advanced & Expert Users stty: error occurs when installing rpm Post 302240009 by Annihilannic on Thursday 25th of September 2008 12:30:56 AM
Old 09-25-2008
Even if you remove the - the scripts are still run as the admin user. I think that is your safest option if the scripts are working like that.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing php-4.3.3-2.i386.rpm

Ok when i try to run the install the is what i get How can i fix this can anyone help (8 Replies)
Discussion started by: Blackrose
8 Replies

2. Shell Programming and Scripting

Installing database through RPM

Hi everyone I have just joined a software developing team. I am new to unix. Basically we are developing a product, the problem is when the end user will install this package we would like to install the datbase associated with our product using RPM. Can it be done? how secure it is? and... (0 Replies)
Discussion started by: atul.saxena
0 Replies

3. HP-UX

Urgent Help needed for Installing RPM on HP-UX

I am working on a HP-UX PARISC 64 architecture. I am trying to install RPM but without success. Has any body successfully installed RPM on the above architecture. I couldnt find a compatible depot file. I tried to compile the source code for rpm-4.0 package. All the dependencies are... (3 Replies)
Discussion started by: sjcekk
3 Replies

4. Shell Programming and Scripting

User installing a rpm package

Hi, I have an application to be installed and I want a user to be able to install it. But I meet the following issues: Removing MyApp error: cannot get exclusive lock on /var/lib/rpm/Packages error: cannot open Packages index using db3 - Operation not permitted (1) error: cannot open... (1 Reply)
Discussion started by: potro
1 Replies

5. Red Hat

Installing rpm packages

Hi guys, I am trying to install some packages for my oracle 11g r2 installation, the below error shows up when I try below: warning: glibc-devel-2.5-24.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186 error: Failed dependencies: glibc-headers is needed by... (8 Replies)
Discussion started by: messi777
8 Replies

6. OS X (Apple)

Installing RPM built on CentOS on Mac OS X

I have a build process that runs on CentOS that builds RPMs for a java-based product. I'd like to be able to install these RPMs on my Mac OS X laptop for testing purposes. I don't need an RPM database to manage dependencies or previously installed packages. Consider this RPM to be a glorified... (1 Reply)
Discussion started by: jschnitter
1 Replies

7. Red Hat

installing rpm from ISO

Hi, I would like to know is it possible to install rpm along its depedable rpm from mounted .iso image on Redhat Linux while installing rpm it is showing so many depandancy, so I would like to know with single command wheather it will take all depedable rpm from mounted iso image. (1 Reply)
Discussion started by: manoj.solaris
1 Replies

8. Red Hat

Installing rpm in centos 6

hi, i am try to install a package in centos 6.2 x86-64 but unable to find any package in centos media iso. In RHEL we have a product folder which contain all the list of rpm but in centos i cant found that. I have use yum command but it also cant work show me the message no module named yum.... (1 Reply)
Discussion started by: zeeshan047
1 Replies

9. AIX

Problem Installing Apache from rpm

I am attempting to install an rpm of Apache from perzl.org on an AIX 6100-07-03-1207 server and it is failing. I think I have all of the dependencies installed. Can anyone help? Any help would be appreciated. It fails with the following error: # rpm -Uvh httpd-2.4.2-2.aix5.1.ppc.rpm ... (3 Replies)
Discussion started by: lbholde
3 Replies

10. AIX

Issue with installing rpm in AIX 6.1

I am trying to install an rpm : libiconv-1.14-1.aix5.1.ppc.rpm which is a dependency to install GIT. While I gave the command I got the foll message: root:user-> $ rpm -i -v libiconv-1.14-1.aix5.1.ppc.rpm libiconv-1.14-1 ar: Cannot open or remove a file containing a running program.... (2 Replies)
Discussion started by: gaugeta
2 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 12:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy