Sponsored Content
Operating Systems Solaris pkgadd changes permissions of /etc Post 302366609 by funwithdolphin on Friday 30th of October 2009 02:25:14 AM
Old 10-30-2009
Question pkgadd changes permissions of /etc

Hi,

when I install a package using pkgadd, it correctly installs the binary files with the user name that I want.

However it also changes the permissions of /etc/rc2.d. I don't want this to happen. I want to retain original owner of /etc/rc2.d as it is.

I could see that before installing, the ownership of the directories is assigned to root:

Code:
bash-2.05# ls -dl /etc
drwxr-xr-x  53  root     sys         3584 Oct  7 17:44 /etc

bash-2.05# ls -dl  /etc/rc2.d
drwxr-xr-x   2 root     sys         1536 Oct  8 16:34  /etc/rc2.d

After installing the package, ownership would be changed and becomes the user which is provided at a time of installation.

Code:
bash-2.05# ls -dl  /etc
drwxr-xr-x  53 cpds42     cpds42         3584 Oct  7 17:44  /etc

bash-2.05# ls -dl /etc/rc2.d
drwxr-xr-x   2 cpds42      cpds42         1536 Oct  8 16:34 /etc/rc2.d

Here is some code snippet of the prototype file:

Code:
# Auto Start/Stop script
  d none /etc 0755 $Owner $Group
  d none /etc/rc2.d 0755 $Owner $Group
  f preserve /etc/rc2.d/S80abc=$SCRIPT_SRC/S80abc 0755 $Owner $Group

I thought the problem is with the above code in prototype file. So I tried changing it to below:
Code:
# Auto Start/Stop script
  d none /etc ? ? ?
  d none /etc/rc2.d ? ? ?
  f preserve /etc/rc2.d/S80abc=$SCRIPT_SRC/S80abc 0755 $Owner $Group

However the problem is still there. It is still changing the existing permissions of /etc and /etc/rc2.d.

Can anyone please give some help pointers?

Last edited by pludi; 10-30-2009 at 08:23 AM.. Reason: code tags, please...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Pkgadd / gnutar

I have sucessfully installed GNUtar using pkgadd but with some questions: When I tried to install with pkgadd -d GNUtar (which is the directory of the package) - I received the error "pkgadd: command not found" Then I tried the same but with pkgadd -d. GNUtar and it installed fine. (found... (4 Replies)
Discussion started by: finster
4 Replies

2. UNIX for Dummies Questions & Answers

pkgadd

I am adding gcc 3.3.2 to my unix box what is the best way to do it???? (4 Replies)
Discussion started by: alsande
4 Replies

3. Solaris

pkgadd

is there an option in pkgadd to accept the default option? I want to use pkgadd in a script and do not want to stop at intercative questions. thx. (6 Replies)
Discussion started by: melanie_pfefer
6 Replies

4. UNIX for Dummies Questions & Answers

pkgadd issues

Please inform me on how I can resolve the PaTcH_MsG 8 Version message below I am running solaris 9 9/05 HW on a Sun V445. Thank you. # pkgadd SUNWqlc Processing package instance <SUNWqlc> from </var/spool/pkg> Qlogic ISP 2200/2202 Fibre Channel Device Driver (sparc)... (3 Replies)
Discussion started by: GLJ@USC
3 Replies

5. UNIX for Advanced & Expert Users

pkgadd issues

I have a server running solaris 8 with veritas 4.1. I am trying to install a package on the server. The package install fails miserably though. I have installed the very same package on other development servers, but for some reason, the install fails on this, soon to be prod, server. No idea... (3 Replies)
Discussion started by: Sowser
3 Replies

6. Solaris

pkgadd help

I'm trying to install a package and it worked on most of the sun boxes and one of the box is just freezing and not going further. Her is the output. pkgadd -d packagename.dstream Select package(s) you wish to process (or 'all' to process all packages). (default: all) : Processing... (1 Reply)
Discussion started by: mokkan
1 Replies

7. Solaris

pkgadd?

Hi all. Is there an option to #pkgadd to test if package bundle you want to install requires a reboot? #pkgadd -d "package bundle" an option like test or a dry run? Suggestions, anyone? :confused: Reloader (2 Replies)
Discussion started by: Reloader
2 Replies

8. Solaris

pkgadd woes

Morning all, I am attempting to load a package from a Solaris 8 CDROM. This fails with the error : "pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap> No changes were made to the system" Any help would be appreciated Andy (6 Replies)
Discussion started by: AndyD
6 Replies

9. Shell Programming and Scripting

pkgadd question

Hi, Please could someone help me, understand how pkgadd works within unix. I have a software file, and I need to package this up and then pkgadd this to another server. Please could some advise me the best way to do this. regards venhart (2 Replies)
Discussion started by: venhart
2 Replies

10. Solaris

Pkgadd with firefox

I am using Solaris 10, and trying to keep a number of old Sun workstations running. Since version 17 of firefox, I have had problems using pkgadd, and had to use tar to un-archive the components of firefox. Is this just a problem with firefox (and probably thunderbird), or is pkgadd broken (1 Reply)
Discussion started by: jkoval
1 Replies
init.d(4)																 init.d(4)

NAME
init.d - initialization and termination scripts for changing init states SYNOPSIS
/etc/init.d /etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro- priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of the states. The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc- tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are incomplete services, and will not be restarted on failure. File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the relative sequence number for killing or starting the job. When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified. Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines. Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line. Example 1: Example of /sbin/rc2. When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The following steps are performed by /sbin/rc2. 1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K. Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below. 2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed. Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by /etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down. svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5) Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica- tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution in relation to managed services are available in svc.startd(1M). On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub- command in svccfg(1M). /sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory. 17 Aug 2005 init.d(4)

Featured Tech Videos

All times are GMT -4. The time now is 02:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy