CN106357454B - Log system control device and control method thereof - Google Patents

Log system control device and control method thereof Download PDF

Info

Publication number
CN106357454B
CN106357454B CN201610876719.0A CN201610876719A CN106357454B CN 106357454 B CN106357454 B CN 106357454B CN 201610876719 A CN201610876719 A CN 201610876719A CN 106357454 B CN106357454 B CN 106357454B
Authority
CN
China
Prior art keywords
log
cmd
client
cloud
file
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.)
Active
Application number
CN201610876719.0A
Other languages
Chinese (zh)
Other versions
CN106357454A (en
Inventor
张磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wuhan Douyu Network Technology Co Ltd
Original Assignee
Wuhan Douyu Network Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Wuhan Douyu Network Technology Co Ltd filed Critical Wuhan Douyu Network Technology Co Ltd
Priority to CN201610876719.0A priority Critical patent/CN106357454B/en
Publication of CN106357454A publication Critical patent/CN106357454A/en
Application granted granted Critical
Publication of CN106357454B publication Critical patent/CN106357454B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Abstract

The invention discloses a log system control device and a control method thereof, and relates to the field of log system control. The log system control device can interact with the client through the cloud after software is sent out, so that the cloud can dynamically control the log system of the client, and the cloud can continuously acquire the log file of the client.

Description

Log system control device and control method thereof
Technical Field
The invention relates to the field of log system control, in particular to a log system control device and a control method thereof.
Background
During software development, developers often add Log (Log) information to the software code. Log information is often a specific reason to help developers locate problems that arise in software. Currently, the designed Log of most software is added during debugging when programmers develop locally, and once software development is completed, the related Log state after software is sent out cannot be changed. That is, the log system cannot be continuously controlled, and the log file of the client cannot be remotely acquired. If the client generates any abnormity in the later period, developers cannot quickly take the corresponding debugging log file, so that the abnormal problems cannot be timely processed.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide the log system control device which can interact with the client through the cloud and enable the cloud to continuously acquire the log file of the client after software is sent out.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows: the utility model provides a log system control device, includes high in the clouds and client, high in the clouds and client establish long connection through the socket, the client sends the heartbeat package to the high in the clouds keeps long connection, the client includes log system, the high in the clouds passes through the socket sends the CMD command extremely log system controls log system opens or closes log system's log information's output, control log system will log information write in the file and form log file, and control log system will log file uploads to the high in the clouds.
On the basis of the technical scheme, the CMD command includes a command CMD _ OPEN _ LOG for opening output of LOG information of the LOG system, a command CMD _ CLOSE _ LOG for closing output of the LOG information of the LOG system, a command CMD _ WRITE _ FILE for writing the LOG information into a FILE, and a command CMD _ SEND _ SERVER for uploading the LOG FILE to the cloud.
On the basis of the technical scheme, the LOG system is provided with a LOG controller, and when the LOG system receives the CMD _ OPEN _ LOG, the LOG controller sets a global variable switch isdibug to true; when the LOG system receives the CMD _ CLOSE _ LOG, the LOG controller sets a global variable switch isdibug as false; when the log system receives the CMD _ WRITE _ FILE, the log controller sets a global variable switch writeToFile to true; when the log system receives the CMD _ SEND _ SERVER, the log controller searches whether a log file exists in a local disk of the client side, if yes, the log controller uploads the log file to the cloud side, and if not, the log controller informs the cloud side that the log file does not exist in the local disk of the client side.
On the basis of the technical scheme, the log system is further provided with a CONSOLE, and the CMD command further comprises a command CMD _ WRITE _ CONSOLE for writing the log information into the CONSOLE and a command CMD _ WRITE _ BOTH for simultaneously writing the log information into the file and the CONSOLE; when the log system receives the CMD _ WRITE _ CONSOLE, the log controller sets a global variable switch writeToConsole to be true; and when the log system receives the CMD _ WRITE _ BOTH, the log controller simultaneously sets the global variable switch writeToConsole and the global variable switch writeToFile to true.
On the basis of the technical scheme, the client is further provided with a third-party pushing software development kit, and the third-party pushing software development kit is respectively connected with the cloud and the client.
Meanwhile, the invention also provides a control method which can enable the cloud side to continuously acquire the log file of the client side through the interaction between the cloud side and the client side after the software is sent out.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows: a method for controlling a log system by using the log system control device comprises the following steps:
establishing long connection between the cloud and the client through a socket, and sending a heartbeat packet to the cloud by the client at regular time to keep the long connection;
the cloud sends a CMD command to a log system of the client, the log system is controlled to open the output of log information of the log system, then the log system is controlled to write the log information into a file to form a log file, and finally the log system is controlled to upload the log file to the cloud.
On the basis of the technical scheme, the cloud end SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ FILE and CMD _ SEND _ SERVER to the LOG system, and a CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isdibug to true and controls the LOG system to output LOG information; the CMD _ WRITE _ FILE command drives a log controller to set a global variable switch writeToFile to true, and a log system is controlled to WRITE log information into a FILE to form a log FILE; and the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist.
On the basis of the technical scheme, the cloud end sends CMD _ WRITE _ CONSOLE to the log system, a CMD _ WRITE _ CONSOLE command drives the log controller to set a global variable switch writeToConsole to be true, and the log system is controlled to WRITE log information into the CONSOLE.
On the basis of the technical scheme, the cloud side SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ BOTH and CMD _ SEND _ SERVER to the LOG system, and the CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isdibug to true and control the LOG system to output LOG information; the CMD _ WRITE _ BOTH command drives the log controller to simultaneously set a global variable switch writeToConsole and a global variable switch writeToFile to true, and a log system is controlled to simultaneously WRITE log information into a console and a file; and the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist.
On the basis of the technical scheme, the cloud end sends a push command containing the CMD command to a third-party push software development kit, the third-party push software development kit wakes up or starts the client end after receiving the push command, the client end establishes long connection with the cloud end through a socket after starting, the client end continues to send a heartbeat package to the cloud end at regular time to keep long connection, then the CMD command sent by the cloud end is processed, and the cloud end continues to control the log system.
Compared with the prior art, the invention has the advantages that:
(1) the log system control device comprises a cloud end and a client end, wherein the cloud end and the client end establish long connection through a socket, and the client end sends a heartbeat packet to the cloud end to keep the long connection. Therefore, the connection between the cloud and the client can be well guaranteed not to be disconnected.
(2) The cloud sends a CMD command to the log system, controls the log system to open or close the output of log information of the log system, controls the log system to write the log information into a file to form a log file, and controls the log system to upload the log file to the cloud. The method and the system can interact with the client through the cloud after the software is sent out, so that the cloud can continuously acquire the log file of the client, and the abnormal problem of the client can be timely processed.
(3) The client side is also provided with a third-party pushing software development kit, and when the socket in the client side cannot be used due to some reasons, the client side is awakened or pulled up through the third-party pushing software development kit, so that the client side can spontaneously establish connection with the cloud side after being started and receive a CMD command issued by the cloud side, and then the client side controls the log controller to execute a corresponding function.
Drawings
FIG. 1 is a schematic diagram of a log system control apparatus of the present invention;
FIG. 2 is a schematic diagram of the working principle and flow of the third party pushing software development kit according to the present invention;
fig. 3 is a flowchart of the log system control device controlling the log system according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings.
Referring to fig. 1, the present invention provides a log system control device, which includes a cloud and a client, where the cloud and the client establish a long connection through a socket, and the client sends a heartbeat packet to the cloud to maintain the long connection.
Two programs on the network exchange data via a bidirectional communication link, one end of which is called a Socket. Socket's english primitive is "hole" or "Socket". The latter meaning is taken as the process communication mechanism of the BSD UNIX. Also commonly referred to as a "socket," which describes an IP address and port, is a handle to a communication chain that may be used to implement communications between different virtual machines or different computers. A host computer on the Internet typically runs a plurality of service software, providing several services simultaneously. Each service opens a socket and binds to a port, with different ports corresponding to different services.
The heartbeat packet is a self-defined command word which is used for regularly informing the self state of the opposite side between the client side and the server, and is sent according to a certain time interval.
In the invention, the cloud terminal can poll the client terminal to send the message or not in the socket communication, and if the cloud terminal does not receive the message received by the client terminal for a long time, the cloud terminal can disconnect the client terminal in order to release the resource occupied by the client terminal. If the cloud end is disconnected from the client end, the client end cannot communicate with the cloud end later, and if the client end wants to continue communication, the client end needs to be connected again. This process of establishing a connection is very time consuming and to solve this problem the client can solve by sending heartbeat packets.
The client side sends heartbeat packets periodically (the heartbeat packet content carries some basic information of the client side, such as a client side mac address, equipment related information, a mobile phone number and the like, and the main purpose is to perform communication operation with the cloud side once), the cloud side finds that the client side communicates with the client side periodically, the cloud side can think that the client side needs service all the time, and the cloud side cannot be disconnected from the client side at the moment. Therefore, the connection between the client and the cloud can be well guaranteed not to be disconnected due to the transmission of the heartbeat packet.
The client comprises a log system, the cloud sends a CMD command to the log system, the log system can be controlled to open or close the output of log information of the log system, the log system is controlled to write the log information into a file to form a log file, and the log system is controlled to upload the log file to the cloud.
The log system is provided with a log controller, and after the log system of the client receives the corresponding CMD command, the client can realize the corresponding function through the log controller, so that the client responds to the action of the CMD command.
The log system is further provided with a control console, and log information of the log system can be written into the control console, so that developers at the client can obtain the log information without downloading log files through the cloud.
Specifically, the cloud and the client perform log system on-off control through a custom protocol, and the cloud and the client define a communication protocol format as follows:
Figure BDA0001126427010000061
Figure BDA0001126427010000071
the CMD commands in the invention have the following expression meanings:
CMD _ OPEN _ LOG: opening log debugging information;
CMD _ CLOSE _ LOG: closing log debugging information;
CMD _ WRITE _ FILE: writing the log information into a file;
CMD _ WRITE _ store: writing the log information into the console;
CMD _ SEND _ SERVER: sending the log file to a server;
CMD _ WRITE _ BOTH: the log information is written to the console while the log is written to the file.
When the log system of the client receives the corresponding command, the client can realize the corresponding function through the log controller. The log controller implementation logic is described below for each command:
CMD _ OPEN _ LOG: opening log debugging information;
1. upon receiving the command, the log controller sets a global variable switch isdibug to true. The isdibug is a bootean variable that controls the global switch of the log controller. It can only process all control command operations when it is in the open state, and the closed state cannot process any operations.
2. When the global variable switch isDebug is in the future, the log system will turn on all log outputs and output log information.
CMD _ CLOSE _ LOG: closing log debugging information;
1. upon receiving this command, the log controller will set a global variable switch isdibug to false.
2. When the global variable switch isdibug is false, the log system can close all log outputs and does not output any log information.
CMD _ WRITE _ FILE: writing the log information into a file;
1. upon receiving the command, the log controller sets a global variable switch writeToFile to true. writeToFile is a switch that writes to a file. On indicates that a file can be written and off indicates that a file cannot be written.
2. When the global variable switch writeToFile is in the future, the log system only outputs the log to the file by default, the default storage path of the file is under the application folder, and the log file is obtained after the log information is written into the file.
CMD _ WRITE _ store: writing the log information into the console;
1. upon receiving this command, the log controller sets a global variable switch writeToConsole to true. writeToConsole is a switch of the write console. An on indicates that the console can be written to, and an off indicates that the console cannot be written to.
2. When the global variable switch writeToConsole is true, the log system will write the log information only to the console.
CMD _ SEND _ SERVER: sending the log file to a server;
1. after receiving the command, the log controller finds the log file on the local disk of the client, if the log file is found, the log file is directly uploaded, and if the log file has many months, the log file in the last month is uploaded by default.
2. If the file is not found, the client does not upload, and information is replied to the cloud to inform the cloud that no log file exists in the client at present.
CMD _ WRITE _ BOTH: writing the log information into a console and simultaneously writing the log information into a file;
1. after receiving the command, the log controller sets the global variable switch writetocosole and the global variable switch writeToFile to true at the same time.
2. After the global variable switch writeToConsole and the global variable switch writeToFile are both true, the log information is written into the console and the file at the same time.
Once the traditional software or the client sends out, the log system can not be controlled basically, and the log file of the client can not be acquired remotely. The log system control device uses heartbeat and long connection to enable the cloud end to keep interaction with the client end. And the cloud end can dynamically allocate the log system by designing issuing of various CMD commands, so that the variability of the log system is achieved, and if the client end is abnormal in a later period, the cloud end can quickly take corresponding debugging log files to quickly solve the abnormal problem.
In addition, if the socket in the client cannot be used due to some reasons, so that the connection between the cloud and the client is broken, the subsequent cloud cannot communicate with the client any more. In order to solve the problem, the client side is further provided with a third-party pushing Software Development Kit (Software Development Kit), and the third-party pushing Software Development Kit is respectively connected with the cloud side and the client side.
The most important characteristic of the push is that the information sent by the cloud can be obtained even if the local application is not started or does not run. After receiving the information sent by the cloud, the client immediately sends a request for establishing a socket with the cloud once the client knows, and if the client is connected, the cloud can normally send a CMD command to communicate with the client and control various behavior operations of a client log system.
The working principle and flow of the third party pushing software development kit are described below with reference to fig. 2:
the cloud end finds that the socket of the client end is disconnected with the cloud end, if the cloud end needs to control the log system of the client end, the cloud end sends a push command to a third-party push software development kit, the main function of the push command is to awaken or start the client end, and meanwhile the push command also comprises information such as a CMD command and the like sent by the cloud end.
After the third-party pushing software development kit receives the request of the cloud, the third-party pushing software development kit immediately wakes up or starts a client program and informs the client of the requirement of the cloud.
After the client is started, a socket connection establishing request is sent to the cloud. After the client and the cloud establish socket connection, the heartbeat packet is still sent to the cloud regularly, then a CMD command issued by the cloud is processed, and if information needs to be fed back, a processing result is fed back to the cloud. After the client and the cloud establish socket connection, the cloud can continue to send the CMD command to the client through the socket.
On the client, the heartbeat connection of the background may be disconnected for the purpose of saving power of the system, and the main purpose is to ensure the power consumption of the system. The cloud end and the client end can be disconnected after the heartbeat connection is disconnected, and once the connection between the client end and the cloud end is disconnected, the cloud end cannot interact with the client end.
In order to solve the problem, the third-party pushing software development kit is arranged at the client, and the pushing module can exist in the background for a long time and cannot be deleted by the system due to the implementation mechanism of the third-party pushing software development kit. Therefore, the cloud can communicate with the pushing module at any time, and after the third-party pushing software development kit receives the corresponding message, the client can be waken up or pulled up, so that the client can spontaneously establish connection with the cloud after being started and receive a CMD command issued by the cloud, and then the client controls the log controller to execute the corresponding function.
Referring to fig. 3, the present invention further provides a method for controlling a log system by using the log system control device, including the following steps:
establishing long connection between the cloud and the client through a socket, and sending a heartbeat packet to the cloud by the client at regular time to keep the long connection;
the cloud sends a CMD command to a log system of the client, the log system is controlled to open the output of log information of the log system, then the log system is controlled to write the log information into a file to form a log file, and finally the log system is controlled to upload the log file to the cloud.
In the invention, the cloud SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ FILE and CMD _ SEND _ SERVER to the LOG system, and a CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isdibug to true and controls the LOG system to output LOG information. And the CMD _ WRITE _ FILE command drives the log controller to set a global variable switch writeToFile to true, and controls the log system to WRITE the log information into the FILE to form a log FILE. And the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist. Therefore, the aim of dynamically allocating the client log system by the cloud is fulfilled.
In order to facilitate the direct acquisition of log information by a client-side worker and avoid sending a request to a cloud-side to acquire the log information, the cloud-side sends CMD _ WRITE _ CONSOLE to a log system, a CMD _ WRITE _ CONSOLE command drives a log controller to set a global variable switch writeToConsole to be true, and the log system is controlled to WRITE the log information into a CONSOLE. Therefore, the staff at the client can directly acquire the log information through the console and timely handle the abnormal problem.
The invention can also control the LOG system to WRITE the LOG information into the console and the file at the same time, the cloud SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ BOTH and CMD _ SEND _ SERVER to the LOG system, the CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isdubu to true, and the LOG system is controlled to output the LOG information; the CMD _ WRITE _ BOTH command drives the log controller to simultaneously set a global variable switch writeToConsole and a global variable switch writeToFile to true, and a log system is controlled to simultaneously WRITE log information into a console and a file; and the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist.
If the socket in the client cannot be used for some reasons, the invention can solve the problem by arranging a third-party push software development kit in the client. The specific process is as follows:
the cloud sends a push command containing the CMD command to a third-party push software development kit;
the third party pushes the software development kit to awaken or start the client after receiving the push command;
after the client is started, long connection is established with the cloud end through a socket, the client continues to send heartbeat packets to the cloud end at regular time to keep long connection, and then a CMD command sent by the cloud end is processed.
And the client side is connected with the cloud side again, and the cloud side can continue to control the log system according to the above-mentioned mode.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.

Claims (7)

1. The utility model provides a log system controlling means, includes high in the clouds and customer end, its characterized in that: the cloud end and the client end establish long connection through a socket, the client end SENDs a heartbeat package to the cloud end to maintain the long connection, the client end comprises a LOG system, the cloud end SENDs a CMD command to the LOG system through the socket, and respectively controls the LOG system to OPEN or CLOSE the output of LOG information of the LOG system through a command CMD _ OPEN _ LOG or CMD _ CLOSE _ LOG, controls the LOG system to WRITE the LOG information into a FILE to form a LOG FILE through a command CMD _ WRITE _ FILE, and controls the LOG system to upload the LOG FILE to the cloud end through a command CMD _ SEND _ SERVER, the client end is further provided with a third-party push software development kit, the third-party push software development kit is respectively connected with the cloud end and the client end, and runs in the background of the client end, when the socket is disconnected, the cloud end is further used for sending a push command containing a CMD command to the third-party push software development kit so as to wake up or start the client.
2. The log system control device as claimed in claim 1, wherein: the LOG system is provided with a LOG controller, and when the LOG system receives the CMD _ OPEN _ LOG, the LOG controller sets a global variable switch isdibug to true; when the LOG system receives the CMD _ CLOSE _ LOG, the LOG controller sets a global variable switch isdibug as false; when the log system receives the CMD _ WRITE _ FILE, the log controller sets a global variable switch writeToFile to true; when the log system receives the CMD _ SEND _ SERVER, the log controller searches whether a log file exists in a local disk of the client side, if yes, the log controller uploads the log file to the cloud side, and if not, the log controller informs the cloud side that the log file does not exist in the local disk of the client side.
3. The log system control device as claimed in claim 2, wherein: the log system is also provided with a CONSOLE, and the CMD command further comprises a command CMD _ WRITE _ CONSOLE for writing the log information into the CONSOLE and a command CMD _ WRITE _ BOTH for simultaneously writing the log information into the file and the CONSOLE; when the log system receives the CMD _ WRITE _ CONSOLE, the log controller sets a global variable switch writeToConsole to be true; and when the log system receives the CMD _ WRITE _ BOTH, the log controller simultaneously sets the global variable switch writeToConsole and the global variable switch writeToFile to true.
4. A method of controlling a log system using the log system control apparatus of claim 1, comprising the steps of:
establishing long connection between the cloud and the client through a socket, and sending a heartbeat packet to the cloud by the client at regular time to keep the long connection;
the cloud SENDs a CMD command to a LOG system of the client, the LOG system is controlled to OPEN the output of LOG information of the LOG system through a command CMD _ OPEN _ LOG, then the LOG system is controlled to WRITE the LOG information into a FILE to form a LOG FILE through a command CMD _ WRITE _ FILE, and finally the LOG FILE is controlled to be uploaded to the cloud through a command CMD _ SEND _ SERVER;
when the socket is disconnected, the cloud end sends a push command containing a CMD command to a third-party push software development kit running in a background of the client, and the third-party push software development kit wakes up or starts the client after receiving the push command.
5. The method of controlling a log system of claim 4, wherein: the cloud SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ FILE and CMD _ SEND _ SERVER to the LOG system, a CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isDebug to true, and the LOG system is controlled to output LOG information; the CMD _ WRITE _ FILE command drives a log controller to set a global variable switch writeToFile to true, and a log system is controlled to WRITE log information into a FILE to form a log FILE; and the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist.
6. The method of controlling a log system of claim 5, wherein: the cloud sends CMD _ WRITE _ CONSOLE to the log system, a CMD _ WRITE _ CONSOLE command drives the log controller to set a global variable switch writeToConsole to be true, and the log system is controlled to WRITE log information into the CONSOLE.
7. The method of controlling a log system of claim 4, wherein: the cloud SENDs CMD _ OPEN _ LOG, CMD _ WRITE _ BOTH and CMD _ SEND _ SERVER to the LOG system, the CMD _ OPEN _ LOG command drives the LOG controller to set the global variable switch isdibug to true, and the LOG system is controlled to output LOG information; the CMD _ WRITE _ BOTH command drives the log controller to simultaneously set a global variable switch writeToConsole and a global variable switch writeToFile to true, and a log system is controlled to simultaneously WRITE log information into a console and a file; and the CMD _ SEND _ SERVER command drives the log controller to search whether the local disk of the client has the log file, if so, the log controller uploads the log file to the cloud, and if not, the log controller informs the local disk of the cloud client that the log file does not exist.
CN201610876719.0A 2016-10-08 2016-10-08 Log system control device and control method thereof Active CN106357454B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610876719.0A CN106357454B (en) 2016-10-08 2016-10-08 Log system control device and control method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610876719.0A CN106357454B (en) 2016-10-08 2016-10-08 Log system control device and control method thereof

Publications (2)

Publication Number Publication Date
CN106357454A CN106357454A (en) 2017-01-25
CN106357454B true CN106357454B (en) 2020-06-16

Family

ID=57866301

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610876719.0A Active CN106357454B (en) 2016-10-08 2016-10-08 Log system control device and control method thereof

Country Status (1)

Country Link
CN (1) CN106357454B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107197040A (en) * 2017-07-03 2017-09-22 北京大生在线科技有限公司 Online remote journal processing method and system for Distance Courseware system
CN109962953A (en) * 2017-12-25 2019-07-02 深圳市优必选科技有限公司 Client communication method for building up and device
CN115134344A (en) * 2022-06-29 2022-09-30 济南浪潮数据技术有限公司 Control method and component of virtual machine console

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101286888A (en) * 2008-05-21 2008-10-15 天柏宽带网络科技（北京）有限公司 Operating method of log system
CN101383880A (en) * 2008-09-26 2009-03-11 中兴通讯股份有限公司 Media gateway log system and log outputting method
CN101465765A (en) * 2008-12-31 2009-06-24 东信和平智能卡股份有限公司 Log system and use method thereof
CN101969386A (en) * 2010-11-09 2011-02-09 道有道(北京)科技有限公司 Log acquisition device and log acquisition method
CN103840953A (en) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 Remote log real-time acquisition method and system
CN103856534A (en) * 2012-12-05 2014-06-11 腾讯科技（深圳）有限公司 Method and system for collecting logs based on peer-to-peer network
CN103942134A (en) * 2014-04-04 2014-07-23 福建星网视易信息系统有限公司 Method and system for viewing embedded device log
CN104539630A (en) * 2015-01-19 2015-04-22 北京网秦天下科技有限公司 Method and device for checking linux journal files at windows client
CN105071958A (en) * 2015-07-29 2015-11-18 上海斐讯数据通信技术有限公司 Server console log management system and method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8930438B2 (en) * 2009-06-17 2015-01-06 Apple Inc. Push-based location update

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101286888A (en) * 2008-05-21 2008-10-15 天柏宽带网络科技（北京）有限公司 Operating method of log system
CN101383880A (en) * 2008-09-26 2009-03-11 中兴通讯股份有限公司 Media gateway log system and log outputting method
CN101465765A (en) * 2008-12-31 2009-06-24 东信和平智能卡股份有限公司 Log system and use method thereof
CN101969386A (en) * 2010-11-09 2011-02-09 道有道(北京)科技有限公司 Log acquisition device and log acquisition method
CN103840953A (en) * 2012-11-21 2014-06-04 中兴通讯股份有限公司 Remote log real-time acquisition method and system
CN103856534A (en) * 2012-12-05 2014-06-11 腾讯科技（深圳）有限公司 Method and system for collecting logs based on peer-to-peer network
CN103942134A (en) * 2014-04-04 2014-07-23 福建星网视易信息系统有限公司 Method and system for viewing embedded device log
CN104539630A (en) * 2015-01-19 2015-04-22 北京网秦天下科技有限公司 Method and device for checking linux journal files at windows client
CN105071958A (en) * 2015-07-29 2015-11-18 上海斐讯数据通信技术有限公司 Server console log management system and method

Also Published As

Publication number Publication date
CN106357454A (en) 2017-01-25

Similar Documents

Publication Publication Date Title
CN105765526B (en) It is guided by network from remote disk mirror image
US7614050B2 (en) Machine and method for deployment of OS image
CN106254179B (en) Heartbeat packet asynchronous control method and device
CN106357454B (en) Log system control device and control method thereof
CN104468397B (en) The method and apparatus that a kind of live migration of virtual machine forwards not packet loss
CN108390927B (en) Method and device for bidirectionally transmitting file between client and virtual machine
CN103916479A (en) Cloud synchronous local area network accelerating system based on working group document
CN108334367A (en) A kind of firmware remote update system and method towards BMC chip
CN104754052A (en) Message pushing method based on Websocket
WO2022032984A1 (en) Mqtt protocol simulation method and simulation device
US10177975B2 (en) Method and apparatus of performing remote management of a managed machine
CN106375476A (en) Method and system for remote startup and shutdown
JP2002268825A (en) System for controlling storage management data
CN204633817U (en) A kind of remote desktop control system
CN112929418B (en) Rapid IO high-speed communication method and system based on publish-subscribe
CN104516687A (en) Windows remote mapping method for Linux block device
EP3826244B1 (en) Congestion control method and related device
JP2006209490A (en) Program for synchronization of set information
CN110086745B (en) Automatic change line data acquisition control system
CN108965368B (en) Data management circuit with network function and data management method based on network
CN112601123A (en) Embedded playing system and method
JP2016118837A (en) Thin client system, and document file control method of thin client
CN112416641A (en) Controlled end node restart detection method in master-slave architecture and master control end node
JP2005308300A (en) Communication protocol interchange device, air conditioning control/monitor device and building managing system
JP6019586B2 (en) Network communication equipment

Legal Events

Date Code Title Description
C06 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