Commit Graph

22 Commits

Author SHA1 Message Date
Jilles Tjoelker
8f8092f8e7 rup: Fix -Wcast-align warnings
Fix possible strict aliasing issue (if time_t is the same size as int but
not int but for example long) which also resulted in a false positive
warning on systems with 64-bit time_t. Pointer casts are bad; we can just
copy the time_t.

Elsewhere, avoid casting char * to int * by using memcpy().

Reviewed by:	eadler
Differential Revision:	https://reviews.freebsd.org/D16075
2018-07-03 19:09:46 +00:00
Eitan Adler
7f08b09a0e rup: compile with WARNS=6 2018-06-25 11:44:53 +00:00
Pedro F. Giffuni
df57947f08 spdx: initial adoption of licensing ID tags.
The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.

Special thanks to Wind River for providing access to "The Duke of
Highlander" tool: an older (2014) run over FreeBSD tree was useful as a
starting point.

Initially, only tag files that use BSD 4-Clause "Original" license.

RelNotes:	yes
Differential Revision:	https://reviews.freebsd.org/D13133
2017-11-18 14:26:50 +00:00
Philip Paeps
5df9daab27 Catch up with 64bit time_t on sparc64. The rstat packet expects a 32bit
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
2005-12-04 18:25:26 +00:00
Ruslan Ermilov
f682f10c76 Sync program's usage() with manpage's SYNOPSIS. 2005-05-21 09:55:10 +00:00
Peter Wemm
ed838bb1cd More xdrproc_t warnings. 2003-10-26 04:57:32 +00:00
Mark Murray
fb46863912 Style only; format function declarations, sort header includes, and
use __FBSDID().
2002-04-28 10:49:15 +00:00
Bill Fenner
2856a77139 If the remote uptime is less than one minute, print the uptime in
seconds instead of leaving the uptime field blank.
2001-10-17 01:44:34 +00:00
Mike Heffner
b1a7433e0b Call clnt_destroy() to prevent exhausting resources.
PR:		bin/14255
Reviewed by:	Kenji Tomita <tommy@ti.com>
MFC after:	2 weeks
2001-06-19 03:48:26 +00:00
Alfred Perlstein
8360efbd6c Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and
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
2001-03-19 12:50:13 +00:00
Warner Losh
62f882d620 getopt and friends are declared in <unistd.h>
getopt returns -1 not EOF.
2000-09-04 06:09:54 +00:00
Peter Wemm
c3aac50f28 $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
Daniel O'Callaghan
5c1bad3122 PR: bin/6193
Submitted by:	Max Euston <meuston@jmrodgers.com>
Make times between 0000-0059 and 1200-1259 show as 12:xx, not 0:xx
1998-04-01 21:34:10 +00:00
Jordan K. Hubbard
9e55697463 Silence a warning with a cast. 1997-09-15 09:46:42 +00:00
Philippe Charnier
692bc4fdc9 Use err(3), so eliminate use of `argv0'. 1997-08-07 06:50:02 +00:00
Peter Wemm
c115df18cd Revert $FreeBSD$ to $Id$ 1997-02-22 19:58:13 +00:00
Jordan K. Hubbard
1130b656e5 Make the long-awaited change from $Id$ to $FreeBSD$
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.
1997-01-14 07:20:47 +00:00
Peter Wemm
399a5e4ac2 Fix bug found by newly visible prototypes in rpc. The code was passing
an in to a function instead of a "struct timeval".
1996-12-30 15:26:51 +00:00
Bill Paul
abc60cd9fc Amend my fix a bit. My way failed to take leap years into account. The
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>
1995-11-21 05:43:27 +00:00
Bill Paul
f7e522bcd5 Rup uses tm_yday in its uptime printout, but ignores tm_year. This means
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. :)
1995-11-19 05:33:30 +00:00
Rodney W. Grimes
7799f52a32 Remove trailing whitespace. 1995-05-30 06:41:30 +00:00
Geoff Rehmet
a82f86e105 rup from FreeBSD 1.1.5.1
Reviewed by:	Geoff
Submitted by:	John Brezak
1994-08-28 15:01:31 +00:00