Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Huntor 1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Huntor 1 (Default branch)
# 1  
Old 10-08-2008
Huntor 1 (Default branch)
Huntor is a full-featured command line Bittorrent client. It currently has no GUI. This client focuses on being run in the background, such as on servers. It is highly customizable. Its disk storage layout makes it easy to incrementally rsync the data to a different machine while downloading. License: Perl License Changes:
All basic parts are implemented, so downloading and uploading should work. Using a tool, settings can be changed at runtime: file preferences can be set and most configuration options can be changed. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT OPENSOLARIS

ypinit

ypinit(1M)						  System Administration Commands						ypinit(1M)

NAME

       ypinit - set up NIS client

SYNOPSIS

       /usr/sbin/ypinit [-c] [-m] [-s master_server]

DESCRIPTION

       ypinit  can  be	used to set up an NIS client system. You must be the superuser to run this command. This script need not be used at all if
       ypbind(1M) is started with the -broadcast option (it is invoked with this option from the svc:/network/nis/client:default service).

       Normally, ypinit is run only once after installing the system. It may be run whenever a new NIS server is added to the network or an exist-
       ing one is decommissioned.

       ypinit  prompts for a list of NIS servers to bind the client to; this list should be ordered from the closest to the furthest server. It is
       recommended that you list each of these NIS servers by name and numeric IP address in /etc/hosts. Though the practice is  not  recommended,
       NIS allows you to list servers by numeric address only, bypassing /etc/hosts. In such a configuration, ypwhich(1) returns a numeric address
       instead of a name.

       ypinit stores the list of servers to which a client can bind in the file /var/yp/binding/domain/ypservers. This file is used by ypbind when
       run without the -broadcast option.

OPTIONS

       -c

	   Set up a ypclient system.

       -m

	   Build a master ypserver data base.

       -s master_server

	   Slave data base. master_server must be the same master configured in the YP maps and returned by the ypwhich -m command.

FILES

       /etc/hosts

	   File in which it is recommended that NIS servers be listed.

       /var/yp/binding/domain/ypservers

	   Lists the servers to which the NIS client is allowed to bind.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWnisu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       svcs(1), ypwhich(1), svcadm(1M), ypbind(1M), sysinfo(2), hosts(4), attributes(5), smf(5)

NOTES

       The NIS client service is managed by the service management facility, smf(5), under the service identifier:

	 svc:/network/nis/client:default

       Administrative  actions	on  this  service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
       vice's status can be queried using the svcs(1) command.

BUGS

       ypinit sets up the list of NIS servers only for the current domain on the system when it is run,  that  is,  the  domain  returned  by  the
       SI_SRPC_DOMAIN command to sysinfo(2). Care should be taken to ensure that this is the same as the desired domain for NIS client processes.

SunOS 5.11							    20 Dec 2007 							ypinit(1M)