Sponsored Content
Full Discussion: Admin privileges check
Top Forums Shell Programming and Scripting Admin privileges check Post 302179269 by era on Thursday 27th of March 2008 10:10:11 AM
Old 03-27-2008
You said you didn't want ad-hockery but here goes anyway. I usually just check for write access to the root directory in my own little admin scripts.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

privileges

I have a website that I am working on and one of the pages allows people to upload pictures to be used on other pages. My question is: is it safe to set the privileges to 777 on the folder that the pictures are saved in? Or would that open up my site to be hacked, bugged, wormed...and everything... (1 Reply)
Discussion started by: paladaxar
1 Replies

2. Programming

root privileges

Hi I have make a program that needs root privleges but any user can try to run it, so what I want it is, when any user tries( other than root ) to run the program, an input prompt would open to enter root password ( if user knows ) and program will run ( otherwise exit ), and after completing... (21 Replies)
Discussion started by: sumsin
21 Replies

3. UNIX for Dummies Questions & Answers

root privileges

Hello, As admin with root rights, to execute any command from another user without password-ask, I do : su - <user> -c "<cmd>" But how can I do to give the same rights to another physical user without using root user ? :confused: I've try to create another user "toor" with the same primary... (4 Replies)
Discussion started by: madmat
4 Replies

4. AIX

copy a fs with the same privileges

Hi All, I use "cp -R /fs/* /newfs" and I can copy everything except it won't have the files/directories the same privileges. Is there a trick to this without using a software-backup. Thanks in advance, itik (3 Replies)
Discussion started by: itik
3 Replies

5. Windows & DOS: Issues & Discussions

Lost Domain Admin Privileges in Samba

Hello, I have apparently lost all domain admin privledges in Samba. I have had several problems ever since I installed the 1/31 Solaris patch cluster. I had to roll out one Samba update (146363-01), which denied all logons network access. However, this particular problem seems to have begun... (0 Replies)
Discussion started by: stringman
0 Replies

6. What is on Your Mind?

Windows Admin switching to *nix Admin

I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies

7. UNIX for Dummies Questions & Answers

Command run with admin privileges

Hi all, I want to run a single command (gdm-restart) which has admin privileges as normal user. I have done these below steps so for. 1. cp -p /usr/sbin/gdm-restart /usr/bin 2. chmod o+w /usr/bin 3. chown user /usr/bin. But still not success. So kindly please let me know whether there is... (3 Replies)
Discussion started by: mastansaheb
3 Replies

8. What is on Your Mind?

Regarding Admin life either as DBA or UNIX Linux admin

I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that. Can we get "DAY" shifts in any one of the admin Job ? Can't we have shift timings in any company ? Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 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:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy