CN106844177A - LINUX blog management methods, device and system - Google Patents
LINUX blog management methods, device and system Download PDFInfo
- Publication number
- CN106844177A CN106844177A CN201710053351.2A CN201710053351A CN106844177A CN 106844177 A CN106844177 A CN 106844177A CN 201710053351 A CN201710053351 A CN 201710053351A CN 106844177 A CN106844177 A CN 106844177A
- Authority
- CN
- China
- Prior art keywords
- storage devices
- nvdimm
- linux
- nvdimm storage
- kernel
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3495—Performance evaluation by tracing or monitoring for systems
Abstract
Present disclose provides a kind of LINUX blog management methods, apparatus and system.Methods described includes:When LINUX system starts, the kernel console of NVDIMM storage devices is registered;In generation system daily record, by the kernel console of the NVDIMM storage devices by the system journal write-in NVDIMM storage devices.The technical scheme of the disclosure can make LINUX system daily record, even if when system occurs abnormal, it is also possible to timely to export, completely preserve and convenient reading, for understanding running situation is provided a great convenience.
Description
Technical field
The disclosure relates generally to field of computer technology, more particularly to a kind of LINUX blog management methods, device and
System.
Background technology
LINUX system daily record is extremely important for understanding LINUX system ruuning situation, especially when exception occurs in system
When, alignment system problem can be helped.For example, system journal can be dispatched in messages files by User space task
Face, in case being checked when needing.But, when LINUX system occurs abnormal, frequently can lead to User space task or system call received
Resistance, system journal can not be synchronized in messages files, so that system journal is lost.
The content of the invention
An aspect of this disclosure provides a kind of LINUX blog management methods, including:When LINUX system starts, note
The kernel console of volume NVDIMM storage devices;In generation system daily record, by the kernel control of the NVDIMM storage devices
Platform processed writes the system journal in the NVDIMM storage devices.
Alternatively, before the kernel console of registration NVDIMM storage devices, also include:Determine whether there is reality in system
Body NVDIMM storage devices;When it is determined that not existing entity NVDIMM storage devices in system, one piece of internal memory is specified from internal memory
As virtual NVDIMM storage devices.
Alternatively, the LINUX blog management methods also include:When system restarts recovery, by described
The kernel console of NVDIMM storage devices reads system journal from the NVDIMM storage devices.
Second aspect of the disclosure provides a kind of LINUX log management apparatus, including:Registering modules, are configured as
When LINUX system starts, the kernel console of NVDIMM storage devices is registered;Journal output module, is configured as producing
During system journal, the system journal is write by the NVDIMM by the kernel console of the NVDIMM storage devices and is stored
In equipment.
Alternatively, LINUX log management apparatus also include:Whether identification module, is configured to determine that in system there is entity
NVDIMM storage devices;Virtual module, is configured as when it is determined that not existing entity NVDIMM storage devices in system, from internal memory
In specify one piece of internal memory as virtual NVDIMM storage devices.
Alternatively, LINUX log management apparatus also include:Log read module, the system of being configured as is restarted extensive
When multiple, system journal is read from the NVDIMM storage devices by the kernel console of the NVDIMM storage devices.
3rd aspect of the disclosure provides a kind of LINUX Log Administration Systems, including:NVDIMM storage devices;With,
At least one processor, by performing executable instruction, realizes the LINUX log management sides that disclosure one side is provided
Method.
Brief description of the drawings
In order to be more fully understood from the disclosure and its advantage, referring now to the following description with reference to accompanying drawing, wherein:
Fig. 1 diagrammatically illustrates the LINUX blog management method flow charts of the embodiment of the disclosure one;
Fig. 2 diagrammatically illustrates the flow chart of the method for the virtual NVDIMM storage devices of the embodiment of the disclosure one;
Fig. 3 diagrammatically illustrates the LINUX blog management method flow charts of another embodiment of the disclosure;
Fig. 4 diagrammatically illustrates the block diagram of the LINUX log management apparatus of the embodiment of the disclosure one;And
Fig. 5 diagrammatically illustrates the block diagram of the LINUX Log Administration Systems of the embodiment of the disclosure one.
Specific embodiment
According to reference to accompanying drawing to the described in detail below of disclosure exemplary embodiment, the other side of the disclosure, advantage
Be will become obvious for those skilled in the art with prominent features.
In the disclosure, term " including " and " containing " and its derivative mean including and it is unrestricted;Term "or" is bag
Containing property, mean and/or.
In this manual, following is explanation for describing the various embodiments of disclosure principle, should not be with any
Mode is construed to the scope of limitation invention.Referring to the drawings described below is used to help comprehensive understanding by claim and its equivalent
The exemplary embodiment of the disclosure that thing is limited.It is described below to help understand including various details, but these details should
Think what is be merely exemplary.Therefore, it will be appreciated by those of ordinary skill in the art that without departing substantially from the scope of the present disclosure and spirit
In the case of, embodiment described herein can be made various changes and modifications.Additionally, for clarity and brevity,
Eliminate the description of known function and structure.Additionally, running through accompanying drawing, same reference numbers are used for identity function and operation.
Shown in the drawings of some block diagrams and/or flow chart.It should be understood that some sides in block diagram and/or flow chart
Frame or its combination can be realized by computer program instructions.These computer program instructions can be supplied to all-purpose computer,
The processor of special-purpose computer or other programmable data processing units, so that these instructions can be with when by the computing device
Create the device for realizing illustrated function/operation in these block diagrams and/or flow chart.
During LINUX system daily record can be by kernel console write-in equipment corresponding with the kernel console, without receiving
The influence of User space task or system call.For example, the external serial equipment of electronic equipment of operation LINUX system can be given, and
The kernel console corresponding with serial equipment is loaded in LINUX system, so that during system journal write into the serial equipment.
But, on the one hand this way needs electron equipment to be equipped with the interface being connected with serial equipment, is on the other hand ensured that
The serial equipment is already attached to electronic equipment and is recognized by LINUX system when LINUX system occurs abnormal.If
When LINUX system occurs abnormal the serial equipment be not connected with electronic equipment or LINUX system it is unidentified go out the serial ports set
It is standby, also result in corresponding system journal and lose.
Each embodiment according to the disclosure provides a kind of LINUX blog management methods.The method is opened in LINUX system
The kernel console of registration NVDIMM storage devices when dynamic;And in generation system daily record, by NVDIMM storage devices
Nuclear control platform writes system journal in NVDIMM storage devices.
According to each embodiment of the disclosure, NVDIMM storage devices integrated DRAM and non-volatile memory chip can
Completely data are preserved when fully powered-off.Therefore, the kernel control of NVDIMM storage devices is registered when LINUX system starts
Platform processed, writes NVDIMM storage devices, and be also not in system when abnormal such as power down occurs in system by system journal in real time
The situation that daily record cannot recover.Therefore, when LINUX system occurs abnormal, the kernel console of NVDIMM storage devices is remained to
In the impregnable write-in NVDIMM storage devices by system journal of enough output functions (printk functions) by system journal.
Also, NVDIMM storage devices are the memory bar specification for being integrated with DRAM and Nonvolatile memory chip, Neng Gou
LINUX system is still completely stored in data therein when restarting recovery.NVDIMM storage devices are in abnormal power-down
When, can be powered by super capacitor, the data in DRAM are saved in nand flash memory;During power up, from nand flash memory
Data are read, state when making DRAM return to power-off.In this way, the system produced when LINUX system occurs abnormal
Daily record can be fully stored in NVDIMM storage devices, and is conveniently checked after LINUX system is restarted, and be for positioning
System problem, removal system failure are provided a great convenience.
According to each embodiment of the disclosure, can first determine whether have in LINUX system before registration NVDIMM storage devices
Entity NVDIMM storage devices.When the NVDIMM storage devices for having entity in LINUX system, you can registration and the entity
The corresponding kernel console of NVDIMM storage devices.In this case, entity is write by NVDIMM kernel consoles
The data of NVDIMM storage devices, in LINUX system either power-off reset or during not power-off reset, all without losing and send out
Any change of life.When in LINUX system in the absence of the NVDIMM storage devices of entity, it is also possible to specified in one piece from internal memory
Deposit as virtual NVDIMM storage devices, then register the corresponding interior nuclear control of the NVDIMM storage device virtual with this
Platform.For virtual NVDIMM storage devices, when LINUX system occurs abnormal, in the case of not power-off reset, Ke Yitong
Cross corresponding mode and obtain system journal from the virtual NVDIMM storage devices.
Fig. 1 diagrammatically illustrates the flow chart of the LINUX blog management methods of the embodiment of the disclosure one.As shown in figure 1, one
The LINUX blog management methods of embodiment are comprised the following steps:
Step 110:When LINUX system starts, the kernel console of NVDIMM storage devices is registered.
The daily record output function of LINUX system is printk functions, by registering NVDIMM storage devices in the present embodiment
Kernel console call printk functions, system journal exported into NVDIMM storage devices.The present embodiment
NVDIMM storage devices can be the NVDIMM storage devices, or virtual NVDIMM storage devices of entity.For reality
The NVDIMM storage devices of body, for example, the NVDIMM that entity can be mounted directly on the electronic equipment of operation LINUX system is deposited
Storage equipment.For the electronic equipment without entity NVDIMM storage devices, it is possible to use virtual NVDIMM technologies, in kernel compiling
When from internal memory specify one piece of internal memory as virtual NVDIMM storage devices.
Step 120:In generation system daily record, system journal is write by the kernel console of NVDIMM storage devices
In NVDIMM storage devices.
System journal can be constantly be generated in LINUX system running.The kernel console of NVDIMM storage devices
Whether real-time monitoring printk functions have system journal to export, when printk function output system daily records are monitored, NVDIMM
The kernel console of storage device exports into corresponding NVDIMM storage devices the system journal obtained from printk functions.
Due to the embedded kernel code execution route of printk functions, do not influenceed by system task scheduling.So as to even if it is different that system occurs
Often, there is panic in such as system, or system call, when going wrong, system journal impregnable can also write
In NVDIMM storage devices.
According to the embodiment of the disclosure one, as shown in Fig. 2 also comprising the steps before the step 110:
Whether step 210, determines there are entity NVDIMM storage devices in system.
In the present embodiment, when LINUX system starts, and registration NVDIMM storage devices kernel console it
Before, whether it is provided with entity NVDIMM storage devices in the electronic equipment for first determining operation LINUX system.For example, in LINUX systems
After system starts, NVDIMM drivers are loaded, whether entity NVDIMM is provided with the electronic equipment of scanning operation LINUX system
Storage device.
Step 220, when it is determined that not existing entity NVDIMM storage devices in system, specifies one piece of internal memory to make from internal memory
It is virtual NVDIMM storage devices.
For example, when kernel is compiled, enabling following option:
Correlation peme (persistent memory) parameter is transmitted when LINUX system starts, one piece is specified in internal memory
Used as virtual NVDIMM storage regions, this virtual NVDIMM storage region will not be used for except nuclear control in NVDIMM internal memory
Outer other the non-designated purposes of platform.Also, position and the content of the data stored in this virtual NVDIMM storage region,
LINUX system not power-off reset and BIOS it is unclear to internal memory sky in the case of, will not change.
The present embodiment is applied in LINUX system the situation of the NVDIMM storage devices in the absence of entity, for without real
The system log management method of the electronic equipment of body NVDIMM storage devices provides a kind of effectively optional mode.
Certainly, in other embodiments, if being provided with entity NVDIMM storage devices in electronic equipment, can be
The corresponding kernel console of entity NVDIMM storage devices is directly registered in LINUX system, and then to NVDIMM storage devices
Carry out reading and writing data.
Fig. 3 diagrammatically illustrates the LINUX blog management method flow charts of another embodiment of the disclosure.As shown in figure 3, another
The LINUX blog management methods of one embodiment include:
Step 310, when LINUX system starts, registers the kernel console of NVDIMM storage devices.
The NVDIMM storage devices of the present embodiment can be that the NVDIMM equipment, or virtual NVDIMM of entity are deposited
Storage equipment.For the NVDIMM storage devices of entity, for example, can be in the electronic equipment of operation LINUX system
NVDIMM storage devices.For the equipment of the storage of the NVDIMM without entity, it is possible to use virtual NVDIMM technologies, in kernel
One piece of internal memory is specified as virtual NVDIMM storage devices from internal memory when compiling.
Step 320, in generation system daily record, is write system journal by the kernel console of NVDIMM storage devices
In NVDIMM storage devices.
The daily record output function of LINUX system is printk functions.In the present embodiment, the kernel control of NVDIMM storage devices
Whether platform real-time monitoring printk functions processed have system journal to export.When printk function output system daily records are monitored,
The kernel console of NVDIMM storage devices exports to corresponding NVDIMM storages the system journal obtained from printk functions
In equipment.Due to the embedded kernel code execution route of printk functions, do not influenceed by system task scheduling.So as to even if hair
During raw system exception, there is panic in such as system, or system call, when going wrong, system journal can be with impregnable
In write-in NVDIMM storage devices.
Step 330, when system reboot recovers, is stored by the kernel console of NVIDIMM storage devices from NVIDIMM
System journal is read in equipment.
In the blog management method of the present embodiment, when LINUX system restarts recovery, especially, for example, it is this restart it is extensive
When multiple by caused by system exception situation, can be deposited from NVIDIMM by the kernel console of NVIDIMM storage devices
The system journal of abnormal conditions is read in storage equipment, so that alignment system problem is helped, for removal system failure is provided greatly
Facility.
Fig. 4 diagrammatically illustrates the block diagram of the LINUX log management apparatus of the embodiment of the disclosure one.As shown in figure 4, one is real
The LINUX log management apparatus 400 for applying example include Registering modules 410 and journal output module 420.The wherein quilt of Registering modules 410
It is configured to be registered when LINUX system starts the kernel console of NVDIMM storage devices;Journal output module 420 is configured
It is, in generation system daily record, system journal to be write by NVDIMM storage devices by the kernel console of NVDIMM storage devices
In.
In the present embodiment, Registering modules 410 register the kernel console of NVDIMM storage devices in LINUX system, use
In the reading and writing data of NVDIMM storage devices.The NVDIMM kernel consoles of registration can be to the data in NVDIMM storage devices
It is read out, shows.NVDIMM storage devices herein can be the NVDIMM equipment of entity, or virtual
NVDIMM storage devices.Wherein for the NVDIMM storage devices of entity, for example, the electronics of system can be grasped in operation LINUX
The NVDIMM storage devices of entity are mounted directly in equipment.For the electronic equipment without entity NVDIMM storage devices, can be with
Using virtual NVDIMM technologies, one piece of internal memory is specified to be set as virtual NVDIMM storages from internal memory when kernel is compiled
It is standby.
In the present embodiment, journal output module 420 is set in LINUX system generation system daily record by NVDIMM storages
Standby kernel console exports into NVDIMM storage devices system journal.The daily record output that journal output module 420 is used
The kernel console of the NVDIMM storage devices that function (printk functions) can be registered Module registers is called.In this way,
Journal output module 420 can be exported to NVDIMM the system journal of generation by the kernel console of NVDIMM storage devices
Storage device.The daily record output function that journal output module 420 is used, i.e. printk functions, embed kernel code execution route,
Do not influenceed by system task scheduling.So as to even if there is system exception, such as panic, or system call occurs in system
When going wrong, the impregnable write-in NVDIMM storage devices of system journal that journal output module 420 will can also be produced
In.
The present embodiment device, as long as whenever LINUX system has system journal, journal output module 420 can
With system journal is registered by Registering modules 410 NVDIMM kernel consoles in real time, in write-in NVDIMM storage devices.
Also, NVDIMM storage devices are the memory bar specifications for being integrated with DRAM and Nonvolatile memory chip, can be in LINUX system
Data therein are still completely stored in when restarting recovery.In this way, the device of the present embodiment can be realized right
Effective output and intact preservation of system journal.
The LINUX log management apparatus 400 of one embodiment also include identification module 430.Identification module 430 is configured as really
Determine whether there are entity NVIDIMM storage devices in system.
Identification module 430 can be by, for example, after LINUX system startup, loading NVDIMM drives journey in systems
Sequence, and scan operation LINUX system electronic equipment in whether be provided with entity NVDIMM storage devices.A kind of situation is to know
Other module 430 recognizes the NVDIMM storage devices that there is entity in system, and Registering modules 410 just can be in LINUX system
Directly register the kernel console of the NVDIMM storage devices of the entity.Another situation is that identification module 430 is recognized less than entity
NVDIMM storage devices, that is, show there is no the NVDIMM storage devices of entity in LINUX system.In this case, can be with
By the virtual NVDIMM storage devices of virtual technology.
The LINUX log management apparatus 400 of one embodiment also include virtual module 440.Virtual module 440 is configured as
When determining not existing entity NVIDIMM storage devices in system, one piece of internal memory is specified to be stored as virtual NVIDIMM from internal memory
Equipment.
Virtual module 440, can be by, for example, in kernel compiling from internal memory during virtual NVIDIMM storage devices
Wait, enable following option:
Virtual module 440 transmits correlation peme (persistent memory) parameter when LINUX system starts, including
Specify one piece of internal memory as virtual NVDIMM storage regions in depositing, this virtual NVDIMM storage region will not be used to remove
Outer other the non-designated purposes of NVDIMM kernel consoles.Also, the position of the data stored in this virtual NVDIMM storage region
Put and content, in LINUX system, power-off reset and BIOS in the case of unclear sky, will not change to internal memory.
In the present embodiment, the setting of virtual module 440 expands the range of application of LINUX log management apparatus 400 so that
The device 400 of the present embodiment can also be applied in the electronic equipment of the NVDIMM storage devices without entity.
The LINUX log management apparatus 400 of one embodiment also include log read module 450.The quilt of log read module 450
It is configured to when system restarts recovery, by the kernel console of NVDIMM storage devices from NVIDIMM storage devices
Read system journal.
When LINUX system restarts recovery, especially, for example, this caused when restarting recovery by system exception situation
When, log read module 450 can be by the kernel console of NVIDIMM storage devices from NVIDIMM storage devices
Read the system journal of abnormal conditions.
The system journal that the LINUX log management apparatus 400 of the present embodiment can produce LINUX system writes NVDIMM
Storage device, and system journal is read from NVDIMM storage devices when LINUX system restarts recovery, it is so as to ensure that
Timely output, complete preservation and the convenient reading of system daily record.The device of the present embodiment, especially occurs abnormal in LINUX system
When, it is that alignment system problem, removal system failure are provided a great convenience.
Fig. 5 diagrammatically illustrates the block diagram of the LINUX Log Administration Systems of the embodiment of the disclosure one.As shown in figure 5,
LINUX Log Administration Systems 500 include processor 510 and NVDIMM storage devices 520.Processor 510 can be, such as general
Microprocessor, instruction set processor and/or related chip group and/or special microprocessor are (for example, application specific integrated circuit
(ASIC)), etc..Processor 510 can also include the onboard storage device for caching purposes.NVDIMM storage devices 520 are wrapped
Include the NVDIMM storage devices 521 and virtual NVDIMM storage devices 522 of entity.Generally, virtual NVDIMM is deposited
Storage equipment 522 is when it is determined that not existing the NVDIMM storage devices of entity in LINUX system, for example, by described by Fig. 2
The method of virtual NVDIMM storage devices, specifies one piece of internal memory as virtual NVDIMM storage devices from internal memory.Processor
510 can be performed for reference to the method flow described by Fig. 1-Fig. 3 any one according to the disclosure each embodiment
The single treatment unit of difference action or multiple processing units.
The LINUX Log Administration Systems 500 of one embodiment can also include being used for receiving letter from other entities and/or module
Number input block 530 and the output unit 540 for providing signal to other entities and/or module.Input block 530
With the entity that output unit 540 can be arranged to single entities or separation.Input block 530 and output unit 540 can
With under the control of the processor 510, for interacting for LINUX Log Administration Systems 500 and LINUX system other parts.
The above method, device, unit and/or module according to each embodiment of the disclosure can be by the electricity that have computing capability
Sub- equipment performs the software comprising computer instruction to realize.The system can include storage device, described above to realize
Various storages.The electronic equipment for having computing capability can be comprising general processor, digital signal processor, dedicated processes
Device, re-configurable processor etc. are able to carry out the device of computer instruction, but not limited to this.Perform such instruction and cause electricity
Sub- equipment is configured as performing the above-mentioned operations according to the disclosure.Above-mentioned each equipment and/or module can be in an electronics
Realized in equipment, it is also possible to realized in distinct electronic apparatuses.These softwares can be stored in a computer-readable storage medium.
Computer-readable recording medium storage one or more programs (software module), one or more of programs include instruction, when
When one or more processors in electronic equipment perform the instruction, the instruction causes that electronic equipment performs the side of the disclosure
Method.
These softwares can be stored as volatile memory or the form of Nonvolatile memory devices (is such as similar to ROM etc.
Storage device), it is whether erasable or rewritable, or form (such as RAM, storage core for being stored as memory
Piece, equipment or integrated circuit), or (such as, CD, DVD, disk or magnetic are stored on light computer-readable recording medium or magnetic computer-readable recording medium
Band etc.).It should be appreciated that storage device and storage medium are adapted for storing the machine readable storage dress of one or more programs
The embodiment put, one program or multiple programs include instruction, when executed, realize the implementation of the disclosure
Example.Embodiment provides the machine-readable storage device of program and this program of storage, and described program is included for realizing the disclosure
Any one claim described in device or method code.Furthermore, it is possible to via any medium (such as, via wired
The signal of communication that connection or wireless connection are carried) to send a telegram here and transmit these programs, multiple embodiments suitably include these programs.
Method, device, unit and/or module according to each embodiment of the disclosure can also use such as field programmable gate
System on array (FPGA), programmable logic array (PLA), on-chip system, substrate, the system in encapsulation, special integrated electricity
Road (ASIC) can come real for carrying out the hardware such as integrated or encapsulation any other rational method or firmware to circuit
It is existing, or realized with software, the appropriately combined of three kinds of implementations of hardware and firmware.The system can include storage device,
To realize storage as described above.When realizing in such ways, software, hardware and/or the firmware for being used be programmed or
It is designed as performing according to the corresponding above method of the disclosure, step and/or function.Those skilled in the art can be according to actual need
Come one or more in these systems and module suitably, or a part therein or some use it is different upper
Implementation is stated to realize.These implementations each fall within the protection domain of the disclosure.
Although the certain exemplary embodiments with reference to the disclosure have shown and described the disclosure, art technology
Personnel it should be understood that in the case of the spirit and scope of the present disclosure limited without departing substantially from appended claims and its equivalent,
The various changes in form and details can be carried out to the disclosure.Therefore, the scope of the present disclosure should not necessarily be limited by above-described embodiment,
But not only should be determined by appended claims, also it is defined by the equivalent of appended claims.
Claims (7)
1. a kind of LINUX blog management methods, including:
When LINUX system starts, the kernel console of NVDIMM storage devices is registered;
In generation system daily record, the system journal is write by the kernel console of the NVDIMM storage devices described
In NVDIMM storage devices.
2. the method for claim 1, wherein also included before the kernel console of registration NVDIMM storage devices:
Determine whether there are entity NVDIMM storage devices in system;
When it is determined that not existing entity NVDIMM storage devices in system, one piece of internal memory is specified from internal memory as virtual NVDIMM
Storage device.
3. the method for claim 1, wherein also include:
When system restarts recovery, set from the NVDIMM storages by the kernel console of the NVDIMM storage devices
Standby middle reading system journal.
4. a kind of LINUX log management apparatus, including:
Registering modules, are configured as being registered when LINUX system starts the kernel console of NVDIMM storage devices;
Journal output module, is configured as in generation system daily record, by the kernel console of the NVDIMM storage devices
By in the system journal write-in NVDIMM storage devices.
5. device according to claim 4, wherein, also include:
Identification module, is configured as
Determine whether there are entity NVDIMM storage devices in system;
Virtual module, is configured as when it is determined that not existing entity NVDIMM storage devices in system, one piece being specified from internal memory
Internal memory is used as virtual NVDIMM storage devices.
6. device according to claim 4, wherein, also include:
Log read module, when the system of being configured as restarts recovery, by the kernel control of the NVDIMM storage devices
Platform processed reads system journal from the NVDIMM storage devices.
7. a kind of LINUX Log Administration Systems, including:
NVDIMM storage devices;
At least one processor, by performing executable instruction, realizes the method as described in claim any one of 1-3.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710053351.2A CN106844177B (en) | 2017-01-23 | 2017-01-23 | LINUX log management method, device and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710053351.2A CN106844177B (en) | 2017-01-23 | 2017-01-23 | LINUX log management method, device and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106844177A true CN106844177A (en) | 2017-06-13 |
CN106844177B CN106844177B (en) | 2020-08-25 |
Family
ID=59120629
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710053351.2A Active CN106844177B (en) | 2017-01-23 | 2017-01-23 | LINUX log management method, device and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106844177B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108170819A (en) * | 2018-01-02 | 2018-06-15 | 联想(北京)有限公司 | A kind of blog management method and device for baseboard management controller |
CN108897634A (en) * | 2018-06-13 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of linux operating system log fault-tolerance approach and system |
CN109426606A (en) * | 2017-08-23 | 2019-03-05 | 东软集团股份有限公司 | Kernel failure diagnosis information processing method, device, storage medium and electronic equipment |
US10776009B2 (en) | 2019-01-03 | 2020-09-15 | International Business Machines Corporation | Journaling on an appendable non-volatile memory module |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101216800A (en) * | 2008-01-02 | 2008-07-09 | 中兴通讯股份有限公司 | LINUX log controller and method |
CN102420756A (en) * | 2011-11-30 | 2012-04-18 | 深圳市共进电子股份有限公司 | Method for storing system logs, and router |
US20140082513A1 (en) * | 2012-09-20 | 2014-03-20 | Appsense Limited | Systems and methods for providing context-sensitive interactive logging |
CN104021093A (en) * | 2014-06-24 | 2014-09-03 | 浪潮集团有限公司 | Power-down protection method for memory device based on NVDIMM (non-volatile dual in-line memory module) |
-
2017
- 2017-01-23 CN CN201710053351.2A patent/CN106844177B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101216800A (en) * | 2008-01-02 | 2008-07-09 | 中兴通讯股份有限公司 | LINUX log controller and method |
CN102420756A (en) * | 2011-11-30 | 2012-04-18 | 深圳市共进电子股份有限公司 | Method for storing system logs, and router |
US20140082513A1 (en) * | 2012-09-20 | 2014-03-20 | Appsense Limited | Systems and methods for providing context-sensitive interactive logging |
CN104021093A (en) * | 2014-06-24 | 2014-09-03 | 浪潮集团有限公司 | Power-down protection method for memory device based on NVDIMM (non-volatile dual in-line memory module) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109426606A (en) * | 2017-08-23 | 2019-03-05 | 东软集团股份有限公司 | Kernel failure diagnosis information processing method, device, storage medium and electronic equipment |
CN108170819A (en) * | 2018-01-02 | 2018-06-15 | 联想(北京)有限公司 | A kind of blog management method and device for baseboard management controller |
CN108897634A (en) * | 2018-06-13 | 2018-11-27 | 郑州云海信息技术有限公司 | A kind of linux operating system log fault-tolerance approach and system |
US10776009B2 (en) | 2019-01-03 | 2020-09-15 | International Business Machines Corporation | Journaling on an appendable non-volatile memory module |
Also Published As
Publication number | Publication date |
---|---|
CN106844177B (en) | 2020-08-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108763099A (en) | Startup method, apparatus, electronic equipment and the storage medium of system | |
CN107357666B (en) | Multi-core parallel system processing method based on hardware protection | |
CN106844177A (en) | LINUX blog management methods, device and system | |
US9158661B2 (en) | Enhanced debugging for embedded devices | |
CN103458036B (en) | Access device and method of cluster file system | |
KR102408053B1 (en) | System on chip, mobile terminal, and method for operating the system on chip | |
US10423783B2 (en) | Methods and apparatus to recover a processor state during a system failure or security event | |
CN101887393B (en) | Equipment fault reproduction method and system based on para-virtualization technique | |
CN103336736B (en) | System log acquisition method and device | |
TWI417744B (en) | Method and system for reconfiguring functional capabilities in a data processing system with dormant resources | |
CN109710317A (en) | System start method, device, electronic equipment and storage medium | |
CN108351826A (en) | Monitor the operation of processor | |
US9703651B2 (en) | Providing availability of an agent virtual computing instance during a storage failure | |
CN106249840A (en) | Power saving non-volatile microprocessor | |
CN114981771A (en) | Memory device recoverable from network attacks and failures | |
CN102622281A (en) | Intelligent terminal and method of data backup and restore thereof | |
JP7091486B2 (en) | Electronic control device, security verification method for electronic control device | |
CN107003882B (en) | Method, system, and apparatus for transforming cache closures and persistent snapshots | |
US9250942B2 (en) | Hardware emulation using on-the-fly virtualization | |
US20210232385A1 (en) | Power Safe Offline Download | |
CN101923500A (en) | Backup and update method and device of bootstrap program in embedded equipment | |
US10896046B2 (en) | Management processor using code from peripheral device | |
CN109507991A (en) | A kind of two axis servo control platform debugging system and method | |
CN111198832B (en) | Processing method and electronic equipment | |
US20180217889A1 (en) | Efficient Transfer of Data from CPU to Onboard Management Device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |