How to determine which SIP a package belongs


 
Thread Tools Search this Thread
Operating Systems Solaris How to determine which SIP a package belongs
# 1  
Old 02-17-2008
How to determine which SIP a package belongs

Hi Folks,

Is there anyway I can determine the package set (or SIP) that a package belongs to. It doesn't seem that pkginfo does it?? I'm trying to remove a whole lot of unecessary packages, and it would be far more convenient if I could remove whole sets at a time instead of indivdual packages.

Cheers.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Emergency UNIX and Linux Support

Problem when trying to remove a package using rpm command - error: package is not installed

Hello, i have installed a package by using the command sudo rpm -i filepackage.rpm package filepackage is already installed when i try to remove it, i get an error saying "is not installed": sudo rpm -e filepackage.rpm error: package filepackage is not installed How can... (4 Replies)
Discussion started by: g_p
4 Replies

2. UNIX for Dummies Questions & Answers

Can't install rpm package with --prefix in new path.Error: package is not relocatable

Hello, i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm" in /usr/local/ directory. I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't. I did: 1st try: Didn't work sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies

3. UNIX for Advanced & Expert Users

How to find dependancies of .dstream package (Solaris) & .rpm package( linux)

Friends, Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ? For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies

4. HP-UX

Determine folder belongs to mountpoint and logical volume

Hi, I would like to know what is command or script to determine the a directory that seat on a logical volume and mount-point. For example: logical volume mount-point ------------ ------------- /dev/vg00/scenario /training/test /dev/vg00/train ... (2 Replies)
Discussion started by: lamoul
2 Replies

5. Debian

How to determine if a package needs a reboot?

Hi, Anyone got a clue? is there some tool for it? couldnt find it in apt get, anyway i hope so cos i must build a patch management tool for work:P Greetz. (10 Replies)
Discussion started by: X-ion
10 Replies

6. UNIX for Dummies Questions & Answers

Tru64 - how can you determine the package where a file or binary belongs to?

Dear linux-unix users, I hope that one of you will be able to help me. How can I determine to which package a file or binary belongs to. With solaris/linux package managers you can easely determine this but i cant find the way how to do this on tru64. Any help would greatly be appreciated.... (0 Replies)
Discussion started by: Crazy_lenny
0 Replies

7. Solaris

Daemon belongs to which package..

If i know a daemon and it is running.. How can i know that daemon belongs to which package? (5 Replies)
Discussion started by: younus_syed
5 Replies

8. Linux

how to restore original package after uninstalling the upgraded package using rpm

have following package installed rpm -qa |grep ADMIN It will give the following package installed: ADMIN-4.0.0.1 Now I will upgrade the ADMIN package using the following command. rpm --upgrade ADMIN-4.1.0.1 It will upgrade the ADMIN packagge to ADMIN-4.1.0.1 Now I want that... (0 Replies)
Discussion started by: amitpansuria
0 Replies
Login or Register to Ask a Question
Net::SIP::Debug(3pm)					User Contributed Perl Documentation				      Net::SIP::Debug(3pm)

NAME
Net::SIP::Debug - debugging of Net::SIP SYNOPSIS
use Net::SIP::Debug 1; use Net::SIP::Debug qw( Net::SIP*=0 Registrar=1 ); Net::SIP::Debug->level(1); perl -MNet::SIP::Debug=1 app.pl DESCRIPTION
Provides debugging support for Net::SIP. Debugging can be enabled/disabled globally or per package and optional per subpackage. It provides support for different debugging levels, e.g. the higher the level, the more debugging is done. The following levels are used: Level 1 Debug messages for users Level 2 Includes short SIP packet dumps of incoming and outgoing data Level 5 Includes detailed SIP packet dumps for incoming and outgoing data Level 10 Includes information about call flow, e.g. why packets get dropped etc. Level 50 Detailed debugging for programmers using Net::SIP. Level 100 Detailed debugging for core developers of Net::SIP. CLASS METHODS
import ( @ARGS ) Extracts everything from arguments given to "use" which might be usable by level and forwards rest to Exporter. If the argument is a reference to a subroutine it will be used for showing the debug message instead of printing it to STDERR. In this case the usual prefixes incl the time will not be added (useful for forwarding debug to syslog). level ( @ARGS ) Enables/disables debugging depending on @ARGS. @ARGS might contain the following specifications: NUMBER NUMBER will be interpreted as the debugging level. It's used in debug etc to print only debug message which a level lower or equal to NUMBER. PACKAGE Enables debugging for package PACKAGE. PACKAGE might be a fully qualified package (e.g. "Net::SIP::Registrar") or the "Net" or "Net::SIP" might be ommited ("Registrar"). If a "*" is added the debugging will also be enabled for subpackages, e.g. "Endpoint*" will enable debugging for Net::SIP::Endpoint and Net::SIP::Endpoint::Context too. PACKAGE=NUMBER Similar to the previous item, but this sets debugging level to NUMBER for the specified packages and thus can also be used to selectivly disable debugging for some packages. If @ARGS is empty it will return the debugging level for the package which called this method (the first package in the caller stack which is not Net::SIP::Debug itself). set_prefix ( PREFIX ) Sets prefix used for debug messages to PREFIX. Default prefix is 'DEBUG:' but for instance for forking applications it might be useful to change this to "DEBUG($$):" or similar. SUBROUTINES
DEBUG|debug ( [ LEVEL ],( MESSAGE | FMT,@ARG )) If debugging is enabled it will print to STDERR debugging info. If multiple arguments are given to the function they will be fed into sprintf to create a single message. If the first argument looks like a number (see looks_like_number in Scalar::Util) it will be interpreted as the debug level for this message, e.g. if it is higher than the user specified debug level the message will not be printed. The MESSAGE (or the result from "sprintf(FMT,@ARG)") will be prefixed by the callers package, the callers function and the line from which DEBUG was called. In front of the prefix the current time (as float time_t) and the string "DEBUG:" will be added. If the message consists of multiple lines each line will be prefixed by the prefix and all but the first line will also have a TAB added between prefix and message data. The function is by default exported as DEBUG and can by exported as debug too. DEBUG_DUMP ( [ LEVEL ], @DATA ) Will call debug with the output from Data::Dumpers Dumper if debugging is enabled. If @DATA has more than one item it will be fed as reference into Dumper, otherwise only the single item will be fed to Dumper. For the meaning of LEVEL see debug. This function is exported by default. stacktrace ( MESSAGE | FMT,@ARG ) Uses the arguments in debug, but instead of writing a debug message to STDERR it will be used in Carp::longmess. Returns string with stacktrace. LEAK_TRACK ( REF ) This is used internally for tracking leaks. It will rebless REF into a new class which behaves like the old one. Calls of LEAK_TRACK and DESTROY on this class will be tracked and shown. If Devel::Peek can be loaded it will Dump information about the REF on each call to LEAK_TRACK. Exported by default. perl v5.14.2 2012-06-26 Net::SIP::Debug(3pm)