diff options
author | Andris Mednis <Andris.Mednis@zabbix.com> | 2021-12-01 15:56:24 +0300 |
---|---|---|
committer | Andris Mednis <Andris.Mednis@zabbix.com> | 2021-12-01 15:56:24 +0300 |
commit | 87415fc54efe5a669a488693fa88c7cf6bdc0f45 (patch) | |
tree | 8d1422a78bdff59361de43f45f2b4d46fe445d8d /src/libs/zbxembed | |
parent | bcd36f288f2e66c8f7bb6a50037d55abd15f7a4d (diff) | |
parent | 22968791f1ff91f3bf8af5a19c89fce2ca24d325 (diff) |
..FG...... [ZBXNEXT-6593] added support of persistent files for restoring log item state after agent restart
* commit '22968791f1ff91f3bf8af5a19c89fce2ca24d325':
...G...... [ZBXNEXT-6593] simplified process_log_check()
...G...... [ZBXNEXT-6593] fixed log message when handling 'mtime' and 'lastlogsize' values restored from persistent file
...G...... [ZBXNEXT-6593] fixed handling of 'mtime' and 'lastlogsize' values restored from persistent file and from server
...G...... [ZBXNEXT-6593] fixed comment in zbx_restore_file_details()
...G...PS. [ZBXNEXT-6593] deleted zbx_psk_hex2bin(), replaced with zbx_hex2bin()
..FG...... [ZBXNEXT-6593] added support of persistent files for restoring log item state after agent restart
Diffstat (limited to 'src/libs/zbxembed')
-rw-r--r-- | src/libs/zbxembed/duktape.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libs/zbxembed/duktape.c b/src/libs/zbxembed/duktape.c index 0d9af216a21..ef20238425c 100644 --- a/src/libs/zbxembed/duktape.c +++ b/src/libs/zbxembed/duktape.c @@ -19971,7 +19971,7 @@ DUK_EXTERNAL void *duk_require_buffer(duk_hthread *thr, duk_idx_t idx, duk_size_ } /* Get the active buffer data area for a plain buffer or a buffer object. - * Return NULL if the the value is not a buffer. Note that a buffer may + * Return NULL if the value is not a buffer. Note that a buffer may * have a NULL data pointer when its size is zero, the optional 'out_isbuffer' * argument allows caller to detect this reliably. */ @@ -56863,7 +56863,7 @@ DUK_INTERNAL duk_uint_fast32_t duk_hobject_pc2line_query(duk_hthread *thr, duk_i * duk_tval copies is not problematic with respect to side effects; * care must be taken when holding and using argument duk_tval pointers. * - * - If a finalizer is executed, it may operate on the the same object + * - If a finalizer is executed, it may operate on the same object * we're currently dealing with. For instance, the finalizer might * delete a certain property which has already been looked up and * confirmed to exist. Ideally finalizers would be disabled if GC |