Sponsored Content
Operating Systems BSD Using pkg_add on alternative host Post 302303575 by figaro on Friday 3rd of April 2009 03:04:04 AM
Old 04-03-2009
Using pkg_add on alternative host

I am using pkg_add to add packages to a FreeBSD 7.1 install. This command is fetching from ftp.freebsd.org, which is known to be slow from my geographical location. Can I set a variable so that the package is fetched from a host closer to the machine (ftp.xx.freebsd.org)?
 

10 More Discussions You Might Find Interesting

1. IP Networking

QNX host cannot ping SCO host, vice versa

The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies

2. UNIX for Advanced & Expert Users

host alias not working: host not found

Hello, I am working on HP-UX , and in the /etc/hosts file we have setup an alias: aa.bb.cc.dd devmach2.unix.org devmach2 devma2v The alias devma2v does not work. Error when pinging devma2v ping: unknown host devma2v For devmach2 the ping works fine , returning the correct IP... (4 Replies)
Discussion started by: FunnyCats
4 Replies

3. Solaris

How to delete the files from local host to remote host

Hi all, i am copying .gz files from production server to development server using "scp" command.my requirement is after copying .gz files i want to delete old .gz files(two days back) in development server from production server. like this way i need to delelte .log ,.z and .dmp files... (3 Replies)
Discussion started by: krishna176
3 Replies

4. UNIX for Dummies Questions & Answers

pkg_add fails

Hi, I have created a package on a 64 bit FreeBSD machine. when i install this (on another 64 bit FreeBSD machine )i get the following error : tar: Skipping pathname containing .. pkg_add: tar extract of /home/vcr/testpackage.tgz failed! pkg_add: unable to extract '/home/vcr/testpackage.tgz'!... (0 Replies)
Discussion started by: HIMANI
0 Replies

5. Shell Programming and Scripting

running commands to remote host from centralized host

Gurus/Experts We have a centralized UNIX/Solaris server from where we can actually ssh to all other UNIX/Solaris servers...I need to write a script that reside on this centerlized server and do FileSystem monitoring (basically run df -h or -k) of other remote servers and then send an email to me... (6 Replies)
Discussion started by: anjum.suri
6 Replies

6. UNIX for Advanced & Expert Users

Help! How to find the local host after few ssh hops to remote host???

I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1. When I do a who -m from A2, I see the "connected from" as "A1". => who -m userid pts/2 2010-03-27 08:47 (A1) I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies

7. UNIX for Dummies Questions & Answers

Transfer large number of files host to host

Hello.... I have two servers, one has an empty / and the other has a subdirectory with a large number (4 gig) with many, many files. I need a way to transfer the files en masse from the server with the large number of files to the one that is essentially blank. I don't have space on the used... (16 Replies)
Discussion started by: blaine.miller
16 Replies

8. IP Networking

ping can not recognize host but host command can

Hi, I have a weird problem. when ever I do ping command like for example ping unix.comI get the following message: # ping unix.com ping: unknown host unix.com but when I use host the computer is able to know the host. # host unix.com unix.com has address 81.17.242.186 unix.com mail is... (2 Replies)
Discussion started by: programAngel
2 Replies

9. Solaris

Need to recover/move diskgroup from failed host to another host

Hi All I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies

10. Shell Programming and Scripting

Connect to target host from Source host.

Hi All, Need to connect to target host and execute a command and connect back to source host to continue with next set of command execution. Is there a utility/command using which we can connect to target host ? Please suggest. Note: Netezza database is instaled on Linux server. ... (4 Replies)
Discussion started by: Nagaraja Akkiva
4 Replies
PKG_DELETE(1)						    BSD General Commands Manual 					     PKG_DELETE(1)

NAME
pkg_delete -- a utility for deleting previously installed software package distributions SYNOPSIS
pkg_delete [-ADFfkNnORrVv] [-K pkg_dbdir] [-P destdir] [-p prefix] pkg-name ... DESCRIPTION
The pkg_delete command is used to delete packages that have been previously installed with the pkg_add(1) command. The given packages are sorted, so that the dependencies needed by a package are deleted after the package. Before any action is executed, pkg_delete checks for packages that are marked as preserved or have depending packages left. If the -k flag is given, preserved packages are skipped and not removed. Unless the -f flag is given, pkg_delete stops on the first error. WARNING
Since the pkg_delete command may execute scripts or programs provided by a package file, your system may be susceptible to ``Trojan horses'' or other subtle attacks from miscreants who create dangerous package files. You are advised to verify the competence and identity of those who provide installable package files. For extra protection, examine all the package control files in the package record directory <PKG_DBDIR>/<pkg-name>/). Pay particular attention to any +INSTALL or +DEINSTALL files, and inspect the +CONTENTS file for @cwd, @mode (check for setuid), @dirrm, @exec, and @unexec directives, and/or use the pkg_info(1) command to examine the installed package control files. OPTIONS
The following command line options are supported: pkg-name ... The named packages are deinstalled, wildcards can be used, see pkg_info(1). If no version is given, the one currently installed will be removed. If the -F flag is given, one or more (absolute) filenames may be specified and the package database will be consulted for the package to which the given file belongs. These packages are then deinstalled. -A Recursively remove all automatically installed packages that were needed by the given packages and are no longer required. Does not remove manually installed packages; see also the -R flag. -D If a deinstallation script exists for a given package, do not execute it. -F Any pkg-name given will be interpreted as pathname which is subsequently transformed in a (real) package name via the package data- base. That way, packages can be deleted by giving a filename instead of the package-name. -f Force removal of the package, even if a dependency is recorded or the deinstall script fails. This might break the package database; see pkg_admin(1) on how to repair it. -ff Force removal of the package, even if the package is marked as a preserved package. Note that this is a dangerous operation. See also the -k option. -K pkg_dbdir Override the value of the PKG_DBDIR configuration option with the value pkg_dbdir. -k Silently skip all packages that are marked as preserved. -N Remove the package's registration and its entries from the package database, but leave the files installed. Don't run any deinstall scripts or @unexec lines either. -n Don't actually deinstall a package, just report the steps that would be taken. -O Only delete the package's entries from the package database; do not touch the package or its files itself. -P destdir Prefix all file and directory names with destdir. For packages without install scripts this has the same behavior as using chroot(8). -p prefix Set prefix as the directory in which to delete files from any installed packages which do not explicitly set theirs. For most pack- ages, the prefix will be set automatically to the installed location by pkg_add(1). -R Recursively remove all packages that were needed by the given packages and are no longer required. This option overrides the -A flag. -r Recursively remove all packages that require one of the packages given. -V Print version number and exit. -v Turn on verbose output. TECHNICAL DETAILS
pkg_delete does pretty much what it says. It examines installed package records in <PKG_DBDIR>/<pkg-name>, deletes the package contents, and finally removes the package records. If a package is required by other installed packages, pkg_delete will list those dependent packages and refuse to delete the package (unless the -f option is given). If a package has been marked as a preserved package, it will not be able to be deleted (unless more than one occurrence of the -f option is given). If a filename is given instead of a package name, the package of which the given file belongs to can be deleted if the -F flag is given. The filename needs to be absolute, see the output produced by the pkg_info(1) -aF command. If a deinstall script exists for the package, it is executed before and after any files are removed. It is this script's responsibility to clean up any additional messy details around the package's installation, since all pkg_delete knows how to do is delete the files created in the original distribution. The deinstall script is called as: deinstall <pkg-name> VIEW-DEINSTALL before removing the package from a view, and as: deinstall <pkg-name> DEINSTALL before deleting all files and as: deinstall <pkg-name> POST-DEINSTALL after deleting them. Passing the keywords VIEW-DEINSTALL, DEINSTALL, and POST-DEINSTALL lets you potentially write only one program/script that handles all aspects of installation and deletion. All scripts are called with the environment variable PKG_PREFIX set to the installation prefix (see the -p option above). This allows a package author to write a script that reliably performs some action on the directory where the package is installed, even if the user might have changed it by specifying the -p option when running pkg_delete or pkg_add(1). The scripts are also called with the PKG_METADATA_DIR environment variable set to the location of the +* meta-data files, and with the PKG_REFCOUNT_DBDIR environment variable set to the location of the package reference counts database directory. If the -P flag was given to pkg_delete, PKG_DESTDIR will be set to destdir. ENVIRONMENT
See pkg_install.conf(5) for options, that can also be specified using the environment. SEE ALSO
pkg_add(1), pkg_admin(1), pkg_create(1), pkg_info(1), pkg_install.conf(5) pkgsrc(7) AUTHORS
Jordan Hubbard most of the work John Kohl refined it for NetBSD Hubert Feyrer NetBSD wildcard dependency processing, pkgdb, recursive "down" delete, etc. Joerg Sonnenberger Rewrote most of the code to compute correct order of deinstallation and to improve error handling. BSD
January 20, 2010 BSD
All times are GMT -4. The time now is 12:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy