Sponsored Content
Operating Systems Solaris how to config sudo in unix boxes Post 302468676 by mtomar on Wednesday 3rd of November 2010 12:58:59 PM
Old 11-03-2010
Go to
site sunfreeware.com
select appropriate solaris version and search for sudo.
It will tell u dependencies if any, download them too. Site has ready to use package. no need to to make all packages from source.

just execute pkgadd -d PKGNAME.

man page is already provided in previous response.
Smilie
hope this help.
 

10 More Discussions You Might Find Interesting

1. Programming

text boxes, radio buttons , check boxes in c++ on unix

Hi ! Please tell me how to get radio buttons, text boxes , check boxes , option buttons , pull down menus in C++ on Unix. I think it would be done using curses.h ..but that's all i know. TIA, Devyani. (3 Replies)
Discussion started by: devy8
3 Replies

2. UNIX for Dummies Questions & Answers

users logging on to unix boxes

I have been asked to write a unix script to log and report all users logging on to our unix boxes as either the root or oracle users only on a 24 hour basis. This should trap the logon and logoff time,if possible what they are doing and their username. Thanks in Advance (2 Replies)
Discussion started by: irehman
2 Replies

3. UNIX for Dummies Questions & Answers

quering unix boxes for attaced printers

Greetings All, I was wanting some info seeing i am a ms geek looking to go into UNIX if i want to query a UNIX box for info regarding printers, LPDs and such source how would i go about this !!!! All comments that would point me in the right direction would be most useful. Cheers (1 Reply)
Discussion started by: seekerO
1 Replies

4. UNIX for Dummies Questions & Answers

What can I ignore when backing up UNIX boxes?

Hi All, Long question and possibly a very short answer.... At work we've just got a new 3rd party backup solution (Netvault by Bakbone -it's v. nice), and I'm currently setting up my UNIX clients as part of the backup schedule. It's just occurred to me that there may be certain files or... (4 Replies)
Discussion started by: geralex
4 Replies

5. Shell Programming and Scripting

Compare files across 2 UNIX boxes

Is it possible to compare two files which reside on different UNIX boxes? (I'm using HP POSIX/Korn) :confused: Consider the scenario of a pre-production environment (box 1) and a production environment (box 2) I would like to check if some files on both boxes match or not. It's quite... (2 Replies)
Discussion started by: flattyre
2 Replies

6. UNIX for Advanced & Expert Users

How to direct-connect two UNIX boxes

Hello, I have a V880 and a 420 running Solaris 9. Each box has more than one NIC card. I'd like to know how to configure the network on the two boxes so that I can directly connect the NIC cards. Meaning, I don't want a switch or router between the two. I just want to run a CAT5 cable to each... (3 Replies)
Discussion started by: agcodba
3 Replies

7. UNIX for Dummies Questions & Answers

Help! Suggestions on what I can I use my 2 unix boxes for?

Once upon a looong time ago I used to work with Unix systems - SGI mainly. Now I've inherited 2 boxes - an SGI dual processor Octane and an Indigo2. For the past 2 years they've sat waiting for me to do something with them and never getting round to it. I run a windows network at home so... (3 Replies)
Discussion started by: JimmyChang
3 Replies

8. UNIX for Dummies Questions & Answers

Dowe have other tools like Putty to connect UNIX boxes

New to UNIX, do we have only putty to work with UNIX boxes remotely ?????? any other tools.. (1 Reply)
Discussion started by: nivaspIND
1 Replies

9. UNIX for Dummies Questions & Answers

problem to determine all files and dir match up on 2 different unix boxes

Hi Friends I have 2 solaris boxes and I need to check certain directories (on local filesystem and mounted nfs) to make sure that they match up on both boxes and to delete or move the other mismatches to elsewhere on the local filesystem. I investigated for unix commands like rsync, and tree... (1 Reply)
Discussion started by: mpc8250
1 Replies

10. Shell Programming and Scripting

monitoring various things (mainly activity) on different unix boxes

Hi there, I want to ask you guys what you think about my problem. I work as a sysadmin on about 7000 workstations or so and to save money and energy, we've decided to switch off as many workstations as possible during the night (probably by shutting it down by cron and power it on by... (8 Replies)
Discussion started by: albator1932
8 Replies
PKG_SUMMARY(5)						      BSD File Formats Manual						    PKG_SUMMARY(5)

NAME
pkg_summary -- summary of binary package repository DESCRIPTION
The file pkg_summary contains information about each package in a binary package repository as a list of variable-value pairs. The variables describing different packages are separated by one empty line. Each line has the format VARIABLE=VALUE. If the value consists of more than one line, each line is prefixed with VARIABLE=. Multi-line variables are guaranteed to be in consecutive lines. The following variables are used: BUILD_DATE (required) The date and time when the package was built. CATEGORIES (required) A list of categories which this package fits in, separated by space. COMMENT (required) A one-line description of the package. CONFLICTS (optional) A list of dewey patterns of packages the package conflicts with, one per line. If missing, this package has no conflicts. DEPENDS (optional) A list of dewey patterns of packages the package depends on, one per line. If missing, this package has no dependencies. DESCRIPTION (required) A more detailed description of the package. FILE_CKSUM (optional) A checksum type supported by digest(1) and checksum separated by space character. FILE_NAME (optional) The name of the binary package file. If not given, PKGNAME.tgz can be assumed. FILE_SIZE (optional) The size of the binary package file, in bytes. HOMEPAGE (optional) A URL where more information about the package can be found. LICENSE (optional) The type of license this package is distributed under. If empty or missing, it is OSI-approved. MACHINE_ARCH (required) The architecture on which the package was compiled. OPSYS (required) The operating system on which the package was compiled. OS_VERSION (required) The version of the operating system on which the package was compiled. PKG_OPTIONS (optional) Any options selected to compile this package. If missing, the package does not support options. PKGNAME (required) The name of the package. PKGPATH (required) The path of the package directory within pkgsrc. PKGTOOLS_VERSION (required) The version of the package tools used to create the package. PREV_PKGPATH (optional) The previous path of the package directory within pkgsrc when a package was moved. (See SUPERSEDES below for a renamed package.) PROVIDES (optional) A list of shared libraries provided by the package, including major version number, one per line. If missing, this pack- age does not provide shared libraries. REQUIRES (optional) A list of shared libraries needed by the package, including major version number, one per line. If missing, this package does not require shared libraries. SIZE_PKG (required) The size of the package when installed, in bytes. SUPERSEDES (optional) A list of dewey patterns of previous packages this package replaces, one per line. This is used for package renaming. The pkg_summary file can be generated using the pkg_info(1) -X option. For example, the following will list this data for all installed packages: pkg_info -X -a SEE ALSO
digest(1), pkg_info(1) HISTORY
The pkg_summary format was first officially documented in April 2006. BSD
April 11, 2009 BSD
All times are GMT -4. The time now is 01:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy