[Bug 11356] New: Busybox used in Motioneye - date setting keeps increasing the year
bugzilla at busybox.net
bugzilla at busybox.net
Sat Sep 15 00:54:02 UTC 2018
https://bugs.busybox.net/show_bug.cgi?id=11356
Bug ID: 11356
Summary: Busybox used in Motioneye - date setting keeps
increasing the year
Product: Busybox
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: kenneth at leewm.com
CC: busybox-cvs at busybox.net
Target Milestone: ---
There’s something not quite right with the “date” command in the MotionEye OS
which makes use of busybox.
I try to set the day to the current date but the resultant year keeps
increasing by 1 each time I do a “date –s”
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20190818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20200818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20210818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20220818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20230818
______________________________________________________________________________
Hi Kenneth,
I tried this myself and saw that strange behavior. I don't know what the cause
could be for that, but:
• this looks like a bug in busybox which provides the date
implementation, so you could report this problem to then
:
:
On Fri, Sep 14, 2018 at 4:19 AM Kenneth Lee <kleewm at gmail.com> wrote:
Hi Calin,
There’s something not quite right with the “date” command in the MotionEye OS.
I try to set the day to the current date but the resultant year keeps
increasing by 1 each time I do a “date –s”
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20190818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20200818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20210818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20220818
[root at meye-09f2c071 etc]# date +%Y%m%d -s 20180914
20230818
[root at meye-09f2c071 etc]#
Rgds
Kenneth
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list