summaryrefslogtreecommitdiffstats
path: root/usr.bin/rup/rup.c
Commit message (Collapse)AuthorAgeFilesLines
* Catch up with 64bit time_t on sparc64. The rstat packet expects a 32bitphilip2005-12-041-5/+19
| | | | | | | | time_t and times will look incorrect on machines with 64bit time_t. PR: 88788 Submitted by: Keith White <Keith.White -at- site.uottawa.ca> MFC after: 1 week
* Sync program's usage() with manpage's SYNOPSIS.ru2005-05-211-1/+1
|
* More xdrproc_t warnings.peter2003-10-261-4/+7
|
* Style only; format function declarations, sort header includes, andmarkm2002-04-281-20/+26
| | | | use __FBSDID().
* If the remote uptime is less than one minute, print the uptime infenner2001-10-171-0/+2
| | | | seconds instead of leaving the uptime field blank.
* Call clnt_destroy() to prevent exhausting resources.mikeh2001-06-191-0/+2
| | | | | | PR: bin/14255 Reviewed by: Kenji Tomita <tommy@ti.com> MFC after: 2 weeks
* Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) andalfred2001-03-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
* getopt and friends are declared in <unistd.h>imp2000-09-041-1/+0
| | | | getopt returns -1 not EOF.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* PR: bin/6193danny1998-04-011-2/+2
| | | | | Submitted by: Max Euston <meuston@jmrodgers.com> Make times between 0000-0059 and 1200-1259 show as 12:xx, not 0:xx
* Silence a warning with a cast.jkh1997-09-151-2/+2
|
* Use err(3), so eliminate use of `argv0'.charnier1997-08-071-22/+19
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Fix bug found by newly visible prototypes in rpc. The code was passingpeter1996-12-301-2/+5
| | | | an in to a function instead of a "struct timeval".
* Amend my fix a bit. My way failed to take leap years into account. Thewpaul1995-11-211-11/+4
| | | | | | | simplest thing is to just calculate the days using curtime - boottime / 86400. The modification for this is less obtrusive anyway. Suggested by: Bill Fenner <fenner@parc.xerox.com>
* Rup uses tm_yday in its uptime printout, but ignores tm_year. This meanswpaul1995-11-191-3/+11
| | | | | | | | that if you do an rup on a machine that's been running longer than a year, you get the wrong day count. Now we factor in 365 * (curtime.tm_year - boottime.tm_year) to get the correct value. (I noticed this while running rup on a SunOS machine I have that's been up 525 days. My FreeBSD machines all said it had only been up for 160 (525-365) days. :)
* Remove trailing whitespace.rgrimes1995-05-301-6/+6
|
* rup from FreeBSD 1.1.5.1csgr1994-08-281-0/+227
Reviewed by: Geoff Submitted by: John Brezak
OpenPOWER on IntegriCloud