2000-08-22 04:34:00 +05:30
|
|
|
/* vi: set sw=4 ts=4: */
|
|
|
|
/*
|
|
|
|
* The Rdate command will ask a time server for the RFC 868 time
|
2012-06-11 05:36:11 +05:30
|
|
|
* and optionally set the system time.
|
2000-08-22 04:34:00 +05:30
|
|
|
*
|
|
|
|
* by Sterling Huxley <sterling@europa.com>
|
|
|
|
*
|
2010-08-16 23:44:46 +05:30
|
|
|
* Licensed under GPLv2 or later, see file LICENSE in this source tree.
|
2016-11-23 16:16:32 +05:30
|
|
|
*/
|
|
|
|
//config:config RDATE
|
2018-12-28 07:50:17 +05:30
|
|
|
//config: bool "rdate (5.6 kb)"
|
2016-11-23 16:16:32 +05:30
|
|
|
//config: default y
|
|
|
|
//config: help
|
2017-07-21 13:20:55 +05:30
|
|
|
//config: The rdate utility allows you to synchronize the date and time of your
|
|
|
|
//config: system clock with the date and time of a remote networked system using
|
|
|
|
//config: the RFC868 protocol, which is built into the inetd daemon on most
|
|
|
|
//config: systems.
|
2016-11-23 16:16:32 +05:30
|
|
|
|
|
|
|
//applet:IF_RDATE(APPLET(rdate, BB_DIR_USR_SBIN, BB_SUID_DROP))
|
|
|
|
|
|
|
|
//kbuild:lib-$(CONFIG_RDATE) += rdate.o
|
2000-08-22 04:34:00 +05:30
|
|
|
|
2011-04-11 06:59:49 +05:30
|
|
|
//usage:#define rdate_trivial_usage
|
2017-01-20 20:33:48 +05:30
|
|
|
//usage: "[-s/-p] HOST"
|
2011-04-11 06:59:49 +05:30
|
|
|
//usage:#define rdate_full_usage "\n\n"
|
2017-01-20 20:33:48 +05:30
|
|
|
//usage: "Set and print time from HOST using RFC 868\n"
|
|
|
|
//usage: "\n -s Only set system time"
|
|
|
|
//usage: "\n -p Only print time"
|
2011-04-11 06:59:49 +05:30
|
|
|
|
2007-05-27 00:30:18 +05:30
|
|
|
#include "libbb.h"
|
2000-08-22 04:34:00 +05:30
|
|
|
|
2007-01-11 22:20:23 +05:30
|
|
|
enum { RFC_868_BIAS = 2208988800UL };
|
2000-08-22 04:34:00 +05:30
|
|
|
|
2008-07-05 14:48:54 +05:30
|
|
|
static void socket_timeout(int sig UNUSED_PARAM)
|
2003-09-12 11:20:51 +05:30
|
|
|
{
|
libbb: reduce the overhead of single parameter bb_error_msg() calls
Back in 2007, commit 0c97c9d43707 ("'simple' error message functions by
Loic Grenie") introduced bb_simple_perror_msg() to allow for a lower
overhead call to bb_perror_msg() when only a string was being printed
with no parameters. This saves space for some CPU architectures because
it avoids the overhead of a call to a variadic function. However there
has never been a simple version of bb_error_msg(), and since 2007 many
new calls to bb_perror_msg() have been added that only take a single
parameter and so could have been using bb_simple_perror_message().
This changeset introduces 'simple' versions of bb_info_msg(),
bb_error_msg(), bb_error_msg_and_die(), bb_herror_msg() and
bb_herror_msg_and_die(), and replaces all calls that only take a
single parameter, or use something like ("%s", arg), with calls to the
corresponding 'simple' version.
Since it is likely that single parameter calls to the variadic functions
may be accidentally reintroduced in the future a new debugging config
option WARN_SIMPLE_MSG has been introduced. This uses some macro magic
which will cause any such calls to generate a warning, but this is
turned off by default to avoid use of the unpleasant macros in normal
circumstances.
This is a large changeset due to the number of calls that have been
replaced. The only files that contain changes other than simple
substitution of function calls are libbb.h, libbb/herror_msg.c,
libbb/verror_msg.c and libbb/xfuncs_printf.c. In miscutils/devfsd.c,
networking/udhcp/common.h and util-linux/mdev.c additonal macros have
been added for logging so that single parameter and multiple parameter
logging variants exist.
The amount of space saved varies considerably by architecture, and was
found to be as follows (for 'defconfig' using GCC 7.4):
Arm: -92 bytes
MIPS: -52 bytes
PPC: -1836 bytes
x86_64: -938 bytes
Note that for the MIPS architecture only an exception had to be made
disabling the 'simple' calls for 'udhcp' (in networking/udhcp/common.h)
because it made these files larger on MIPS.
Signed-off-by: James Byrne <james.byrne@origamienergy.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
2019-07-02 15:05:03 +05:30
|
|
|
bb_simple_error_msg_and_die("timeout connecting to time server");
|
2003-09-12 11:20:51 +05:30
|
|
|
}
|
|
|
|
|
2001-03-20 01:11:54 +05:30
|
|
|
static time_t askremotedate(const char *host)
|
2000-08-22 04:34:00 +05:30
|
|
|
{
|
2007-01-11 22:20:23 +05:30
|
|
|
uint32_t nett;
|
2000-08-22 04:34:00 +05:30
|
|
|
int fd;
|
|
|
|
|
2017-07-27 18:01:59 +05:30
|
|
|
/* Timeout for dead or inaccessible servers */
|
2003-09-12 11:20:51 +05:30
|
|
|
alarm(10);
|
|
|
|
signal(SIGALRM, socket_timeout);
|
|
|
|
|
2018-04-17 16:13:54 +05:30
|
|
|
fd = create_and_connect_stream_or_die(host, bb_lookup_std_port("time", "tcp", 37));
|
2001-03-20 01:11:54 +05:30
|
|
|
|
2012-06-11 05:36:11 +05:30
|
|
|
if (safe_read(fd, &nett, 4) != 4) /* read time from server */
|
2015-02-18 18:17:27 +05:30
|
|
|
bb_error_msg_and_die("%s: %s", host, "short read");
|
2012-06-11 05:36:11 +05:30
|
|
|
if (ENABLE_FEATURE_CLEAN_UP)
|
|
|
|
close(fd);
|
2000-08-22 04:34:00 +05:30
|
|
|
|
2012-06-11 05:36:11 +05:30
|
|
|
/* Convert from network byte order to local byte order.
|
2017-07-27 18:01:59 +05:30
|
|
|
* RFC 868 time is seconds since 1900-01-01 00:00 GMT.
|
|
|
|
* RFC 868 time 2,208,988,800 corresponds to 1970-01-01 00:00 GMT.
|
2012-06-11 05:36:11 +05:30
|
|
|
* Subtract the RFC 868 time to get Linux epoch.
|
2000-08-22 04:34:00 +05:30
|
|
|
*/
|
2017-01-20 20:33:48 +05:30
|
|
|
nett = ntohl(nett) - RFC_868_BIAS;
|
|
|
|
|
|
|
|
if (sizeof(time_t) > 4) {
|
|
|
|
/* Now we have 32-bit lsb of a wider time_t
|
|
|
|
* Imagine that nett = 0x00000001,
|
|
|
|
* current time cur = 0x123ffffffff.
|
|
|
|
* Assuming our time is not some 40 years off,
|
|
|
|
* remote time must be 0x12400000001.
|
2017-07-27 18:01:59 +05:30
|
|
|
* Need to adjust our time by (int32_t)(nett - cur).
|
2017-01-20 20:33:48 +05:30
|
|
|
*/
|
|
|
|
time_t cur = time(NULL);
|
|
|
|
int32_t adjust = (int32_t)(nett - (uint32_t)cur);
|
|
|
|
return cur + adjust;
|
|
|
|
}
|
|
|
|
/* This is not going to work, but what can we do */
|
|
|
|
return (time_t)nett;
|
2000-08-22 04:34:00 +05:30
|
|
|
}
|
|
|
|
|
2007-10-11 15:35:36 +05:30
|
|
|
int rdate_main(int argc, char **argv) MAIN_EXTERNALLY_VISIBLE;
|
2008-07-05 14:48:54 +05:30
|
|
|
int rdate_main(int argc UNUSED_PARAM, char **argv)
|
2000-08-22 04:34:00 +05:30
|
|
|
{
|
2001-03-21 13:04:27 +05:30
|
|
|
time_t remote_time;
|
2012-06-11 05:36:11 +05:30
|
|
|
unsigned flags;
|
2006-01-25 05:38:53 +05:30
|
|
|
|
2017-08-09 01:25:02 +05:30
|
|
|
flags = getopt32(argv, "^" "sp" "\0" "-1");
|
2006-01-25 05:38:53 +05:30
|
|
|
|
2001-03-21 13:04:27 +05:30
|
|
|
remote_time = askremotedate(argv[optind]);
|
2001-03-20 01:11:54 +05:30
|
|
|
|
2017-01-20 20:33:48 +05:30
|
|
|
/* Manpages of various Unixes are confusing. What happens is:
|
|
|
|
* (no opts) set and print time
|
|
|
|
* -s: set time ("do not print the time")
|
|
|
|
* -p: print time ("do not set, just print the remote time")
|
|
|
|
* -sp: print time (that's what we do, not sure this is right)
|
|
|
|
*/
|
|
|
|
|
2012-06-11 18:27:29 +05:30
|
|
|
if (!(flags & 2)) { /* no -p (-s may be present) */
|
2017-01-20 20:37:14 +05:30
|
|
|
if (time(NULL) == remote_time)
|
libbb: reduce the overhead of single parameter bb_error_msg() calls
Back in 2007, commit 0c97c9d43707 ("'simple' error message functions by
Loic Grenie") introduced bb_simple_perror_msg() to allow for a lower
overhead call to bb_perror_msg() when only a string was being printed
with no parameters. This saves space for some CPU architectures because
it avoids the overhead of a call to a variadic function. However there
has never been a simple version of bb_error_msg(), and since 2007 many
new calls to bb_perror_msg() have been added that only take a single
parameter and so could have been using bb_simple_perror_message().
This changeset introduces 'simple' versions of bb_info_msg(),
bb_error_msg(), bb_error_msg_and_die(), bb_herror_msg() and
bb_herror_msg_and_die(), and replaces all calls that only take a
single parameter, or use something like ("%s", arg), with calls to the
corresponding 'simple' version.
Since it is likely that single parameter calls to the variadic functions
may be accidentally reintroduced in the future a new debugging config
option WARN_SIMPLE_MSG has been introduced. This uses some macro magic
which will cause any such calls to generate a warning, but this is
turned off by default to avoid use of the unpleasant macros in normal
circumstances.
This is a large changeset due to the number of calls that have been
replaced. The only files that contain changes other than simple
substitution of function calls are libbb.h, libbb/herror_msg.c,
libbb/verror_msg.c and libbb/xfuncs_printf.c. In miscutils/devfsd.c,
networking/udhcp/common.h and util-linux/mdev.c additonal macros have
been added for logging so that single parameter and multiple parameter
logging variants exist.
The amount of space saved varies considerably by architecture, and was
found to be as follows (for 'defconfig' using GCC 7.4):
Arm: -92 bytes
MIPS: -52 bytes
PPC: -1836 bytes
x86_64: -938 bytes
Note that for the MIPS architecture only an exception had to be made
disabling the 'simple' calls for 'udhcp' (in networking/udhcp/common.h)
because it made these files larger on MIPS.
Signed-off-by: James Byrne <james.byrne@origamienergy.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
2019-07-02 15:05:03 +05:30
|
|
|
bb_simple_error_msg("current time matches remote time");
|
2003-12-19 16:59:29 +05:30
|
|
|
else
|
|
|
|
if (stime(&remote_time) < 0)
|
libbb: reduce the overhead of single parameter bb_error_msg() calls
Back in 2007, commit 0c97c9d43707 ("'simple' error message functions by
Loic Grenie") introduced bb_simple_perror_msg() to allow for a lower
overhead call to bb_perror_msg() when only a string was being printed
with no parameters. This saves space for some CPU architectures because
it avoids the overhead of a call to a variadic function. However there
has never been a simple version of bb_error_msg(), and since 2007 many
new calls to bb_perror_msg() have been added that only take a single
parameter and so could have been using bb_simple_perror_message().
This changeset introduces 'simple' versions of bb_info_msg(),
bb_error_msg(), bb_error_msg_and_die(), bb_herror_msg() and
bb_herror_msg_and_die(), and replaces all calls that only take a
single parameter, or use something like ("%s", arg), with calls to the
corresponding 'simple' version.
Since it is likely that single parameter calls to the variadic functions
may be accidentally reintroduced in the future a new debugging config
option WARN_SIMPLE_MSG has been introduced. This uses some macro magic
which will cause any such calls to generate a warning, but this is
turned off by default to avoid use of the unpleasant macros in normal
circumstances.
This is a large changeset due to the number of calls that have been
replaced. The only files that contain changes other than simple
substitution of function calls are libbb.h, libbb/herror_msg.c,
libbb/verror_msg.c and libbb/xfuncs_printf.c. In miscutils/devfsd.c,
networking/udhcp/common.h and util-linux/mdev.c additonal macros have
been added for logging so that single parameter and multiple parameter
logging variants exist.
The amount of space saved varies considerably by architecture, and was
found to be as follows (for 'defconfig' using GCC 7.4):
Arm: -92 bytes
MIPS: -52 bytes
PPC: -1836 bytes
x86_64: -938 bytes
Note that for the MIPS architecture only an exception had to be made
disabling the 'simple' calls for 'udhcp' (in networking/udhcp/common.h)
because it made these files larger on MIPS.
Signed-off-by: James Byrne <james.byrne@origamienergy.com>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
2019-07-02 15:05:03 +05:30
|
|
|
bb_simple_perror_msg_and_die("can't set time of day");
|
2006-06-03 15:54:20 +05:30
|
|
|
}
|
2006-01-25 05:38:53 +05:30
|
|
|
|
2012-06-11 18:27:29 +05:30
|
|
|
if (flags != 1) /* not lone -s */
|
2006-06-03 15:54:20 +05:30
|
|
|
printf("%s", ctime(&remote_time));
|
2000-08-22 04:34:00 +05:30
|
|
|
|
2000-12-01 08:25:13 +05:30
|
|
|
return EXIT_SUCCESS;
|
2000-08-22 04:34:00 +05:30
|
|
|
}
|