On Tue, Dec 5, 2017 at 11:14 PM, Qi, Fuli <qi.fuli(a)jp.fujitsu.com> wrote:
On 2017/11/21 6:19, Dan Williams wrote:
> On Mon, Nov 13, 2017 at 11:46 PM, QI Fuli <qi.fuli(a)jp.fujitsu.com> wrote:
>> This patch is used to provide helper functions needed for nvdimm daemon.
>> These util functions can be used by other features as well in the future.
>> Signed-off-by: QI Fuli <qi.fuli(a)jp.fujitsu.com>
>> nvdimmd/util.c | 80
>> nvdimmd/util.h | 33 ++++++++++++++++++++++++
>> 2 files changed, 113 insertions(+)
>> create mode 100644 nvdimmd/util.c
>> create mode 100644 nvdimmd/util.h
>> diff --git a/nvdimmd/util.c b/nvdimmd/util.c
>> new file mode 100644
>> index 0000000..ef6819e
>> --- /dev/null
>> +++ b/nvdimmd/util.c
>> @@ -0,0 +1,80 @@
>> + * Copyright (c) 2017, FUJITSU LIMITED. All rights reserved.
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * under the terms and conditions of the GNU Lesser General Public
>> + * version 2.1, as published by the Free Software Foundation.
>> + *
>> + * This program is distributed in the hope it will be useful, but
>> WITHOUT ANY
>> + * WARRANTY; without even the implied warranty of MERCHANTABILITY or
>> + * FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License
>> + * more details.
>> + */
>> +#include <stdlib.h>
>> +#include <string.h>
>> +#include <time.h>
>> +#include "util.h"
>> +void logrotate(char *file)
>> + time_t c_time;
>> + char buf, tstamp;
>> + c_time = time(NULL);
>> + strftime(tstamp, sizeof(tstamp), ".%Y%m%d%H%M%S",
>> + strcpy(buf, file);
>> + strcat(buf, tstamp);
>> + rename(file, buf);
> Why does the monitor need to rotate logs? This should be the
> responsibility of whatever is consuming the nvdimmd events.
When I wrote it, I thought that users can rotate nvdimmd logs without using
If you think it is not necessary, I will remove it in next version.
In general we should let other system components handle the mechanics
they are responsible to handle. In this case as long as nvdimmd
reports the log message to the systemd-journal or the platform's
syslog facility then it has done its job and the log machinery is
responsible for rotation.
I've also been giving more thought about the command line interface
for the monitor. I think it should reuse the "ndctl list"
infrastructure for selecting and filtering devices so the user can
launch monitors like this:
ndctl monitor --dimms --namespace=namespace0.0 --action=page_admin.sh
ndctl monitor -BDRN --action=log
Where those commands would run the 'page admin' script if any DIMM
event happens on any DIMM associated with namespace0.0, and log
everything else" that happens on any other device. We likely also need
"--event=" to control the events to filter, and a --list-events option
to enumerate all the possible events.