CN116955303A - Shared directory management method, device, electronic equipment and medium - Google Patents

Abstract

The disclosure provides a shared directory management method, a shared directory management device, electronic equipment and a medium, which can be used in the financial field or other fields. Adapted to execute in a computing device having an operating system present therein, the method comprising: configuring a management program in an operating system and installing the management program, and calling and operating the management program after the installation is completed by selecting a network sharing page in a file resource manager; the management program comprises a task planning program, wherein the task planning program comprises a management task, and the management task is used for starting the management program at fixed time; setting the host user authority of a management program, creating a current shared directory, setting the access authority of other users, and starting the current shared directory; after the current shared directory completes sharing, the management task executes and closes the current shared directory; and unloading the management program after closing the current shared directory. The method effectively solves the information security risk, realizes a safe sharing environment, and uses the sharing directory conveniently and rapidly.

Description

A shared directory management method, device, electronic equipment and media

Technical field

The present invention can be used in the financial field or other fields, and more specifically relates to a shared directory management method, device, electronic equipment, storage medium and program product.

Background technique

Sharing document directories with other users and different terminals is an important way of document transmission. It is also an important data transmission method between Xinchuang terminals and traditional Windows terminals. It is commonly used in the current office transaction process. According to the current regulations on information security management, directory sharing must implement the minimum authorization principle, and users must be accurately authorized. Sharing should be closed as soon as possible after use. The shared directory is opened and closed very frequently for this reason.

We currently use a WindowsAD domain architecture centralized directory management service environment, and each user is assigned a separate user name. If a user shares his directory for others to access, he needs to use the "directory sharing" function of the Windows operating system. In actual operation, the sharing setting process is relatively complicated and requires several steps. The main users are business personnel, whose professional capabilities in operating systems are generally insufficient. The operation process is prone to problems such as expansion of authorization rights and authorization to everyone. After the shared access is completed, you must remember to close the sharing in time. Certain information security risk events may easily occur if you are not careful.

Currently, the Windows 10 system has three implementation methods for enabling sharing of the current directory and the existing defects.

The first method steps are: click, Properties → Sharing → Advanced Sharing → Adjust authorized users and permissions → Shared directory.

There is a problem: "Everyone full control" permission exists (to everyone), and other authorized user information is missing. Violating information management requirements, Everyone needs to be deleted and then added with missing authorized usernames and permissions. After the shared directory is deleted, the authorized user names and permissions added when sharing is enabled in the permission table are not deleted simultaneously and must be deleted manually. After clicking "Edit" to delete the authorized user, the memory of the user name and permissions will disappear. Each time sharing is reopened, the authorized user name and permissions must be reset.

The steps of the second method are: click, Properties → Sharing → Advanced Sharing → Share this folder → Permissions → Everyone read permission (to everyone), you must first delete Everyone, then add the authorized user name and permissions → OK. Properties → Security → Edit → Add missing authorized user names and permissions → OK.

There is a problem: Everyone needs to be deleted and then the missing authorized username and permissions added. There is no permission memory function, and the authorized user name and permissions must be reset every time sharing is enabled. After the shared directory is deleted, the authorized users and permissions added when sharing is enabled in the permission table of Properties → Security (User Access Control Authorization) are not deleted simultaneously and must be deleted manually. After clicking "Edit" to delete the authorized user, the memory of the user name and permissions will disappear. Each time sharing is reopened, the authorized user name and permissions must be reset.

The steps of the third method are: click, authorize access rights → specific users → adjust authorized users and permissions → share.

There is a problem: other authorized users are missing, which violates information management requirements. Everyone needs to be deleted and then the missing authorized user names and permissions are added. After the shared directory is deleted, the authorized user names and permissions added when sharing is enabled in the permission table of Properties → Security (User Access Control Authorization) are not deleted simultaneously and must be deleted manually. After clicking "Edit" to delete the authorized user name, the memory of the user name and permissions will disappear. Each time sharing is reopened, the authorized user name and permissions must be reset.

Compared with the information security management requirements, there are three obvious problems in the above three methods:

(1) There is a hidden danger of expanding access rights (it is easy to grant access rights to Everyone).

(2) After sharing is turned off, the authorized users added when sharing is turned on are not cleared simultaneously.

(3) You must always remember to close the sharing in time after the shared access is completed. The operability and efficiency are very low.

In order to prevent the above three existing problems and avoid the above problems, a shared directory management method is provided. A management program is configured in the operating system and installed. The program runs in the Windows environment and can conveniently open and close sharing. , automatically clear timeout sharing, automatically clear user permissions, and clear authorized user permissions, effectively solving the above information security risks, realizing a safe and convenient file sharing environment, facilitating safe, compliant and convenient use of shared directories, and reducing operating system resource overhead.

Contents of the invention

In view of the above problems, the present disclosure provides a shared directory management method, device, electronic device, storage medium and program product.

According to a first aspect of the present disclosure, a shared directory management method is provided, which is suitable for execution in a computing device. There is an operating system in the computing device. The method includes: configuring a management program in the operating system and installing the management program, by Select the network sharing page in the file explorer, call and run the management program after the installation is completed; the management program includes the task scheduler, the task scheduler includes the management tasks, and the management tasks are used to start the management program regularly; set the host of the management program User permissions, create the current shared directory and set the access permissions of other users, open the current shared directory; after the current shared directory is shared, the management task is executed to close the current shared directory; after the current shared directory is closed, the management program is uninstalled.

According to an embodiment of the present disclosure, setting the host user permissions of the management program, creating the current shared directory and setting the access permissions of other users, and opening the current shared directory include: determining whether the host user permissions are set for the first time, and if so, changing the host user permissions Set as the permission information of the current host user; otherwise, retain the last set permission information as the host user permission; call the operating system's creation command to create the current shared directory; call the operating system's access command to set the access permission information of other users ;Save host user permission information and other users' access permission information.

According to an embodiment of the present disclosure, calling the creation instruction of the operating system to create the current shared directory includes: using a system management tool to obtain the first object, using the attributes of the first object to access the generated shared directory list in the computing device; traversing the computing device The generated shared directory list is compared with the directory name of the current shared directory until the directory name of the current shared directory is not repeated.

According to an embodiment of the present disclosure, the management task is used to perform any one of the following operations: calling task instructions of the operating system to perform management tasks in the task scheduler; running the task scheduler; starting the management program regularly; or closing the current shared directory ; Among them, closing the current shared directory includes: traversing the shared directory list that has been generated in the computing device, and comparing the difference between the sharing time of the generated shared directory and the sharing time of the current shared directory; the sharing time of the generated shared directory will be exceeded And the current shared directory with abnormal time information is closed, and the permission information of the current shared directory is cleared.

According to an embodiment of the present disclosure, closing the current shared directory further includes: calling a shutdown instruction of the operating system, using a system management tool to obtain a second object, and using attributes of the second object to access the generated shared directory list and the current shared directory in the computing device. Shared directory; traverse the generated shared directory list and the current shared directory in the computing device, and use the attributes of the second object to clear the permission information of the current shared directory.

According to embodiments of the present disclosure, by adjusting parameters of the management program, the sharing time of the current shared directory is adjusted and the permission information of the current shared directory is cleared regularly.

According to an embodiment of the present disclosure, the parameters of the management program include: the duration of the current shared directory, the start time of cleaning the current shared directory, and the management time of the current shared directory.

According to an embodiment of the present disclosure, a shared directory management method further includes: calling instructions for use of the operating system and displaying instructions for the management program. The instructions for use include function introduction, usage methods and precautions.

According to an embodiment of the present disclosure, after closing the current shared directory, uninstalling the management program includes: deleting the network sharing page in the file explorer; deleting the management task in the task scheduler; clearing the generated shared directory in the computing device List and current shared directory.

A second aspect of the present disclosure provides a shared directory management device, which is suitable for execution in a computing device. There is an operating system in the computing device. The shared directory management device includes: a program installation module for configuring a management program in the operating system and Install the management program and select the network share page in the file explorer to call and run the management program after the installation is completed; the management program includes the task scheduler, the task scheduler includes management tasks, and the management task is used to start the management program regularly. ; The shared directory opening module is used to set the host user permissions of the management program, create the current shared directory and set the access permissions of other users, and open the current shared directory; the shared directory closing module is used to manage tasks after the current shared directory is shared. Execute closing of the current shared directory; the program uninstall module is used to uninstall the management program after closing the current shared directory.

A third aspect of the present disclosure provides an electronic device, including: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors When, one or more processors are caused to execute the above shared directory management method.

A fourth aspect of the present disclosure also provides a computer-readable storage medium on which executable instructions are stored. When executed by a processor, the instructions cause the processor to perform the above shared directory management method.

A fifth aspect of the present disclosure also provides a computer program product, including a computer program that implements the above shared directory management method when executed by a processor.

Description of the drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

Figure 1 schematically shows the system architecture of a shared directory management method and device according to an embodiment of the present disclosure.

Figure 2 schematically shows a flow chart of a shared directory management method according to an embodiment of the present disclosure.

FIG. 3 schematically illustrates a flow chart of a process of installing and running a hypervisor according to an embodiment of the present disclosure.

Figure 4 schematically shows a flow chart of a process of opening a shared directory according to an embodiment of the present disclosure.

Figure 5 schematically shows a flow chart of shared directory management program uninstallation according to an embodiment of the present disclosure.

Figure 6 schematically shows a block diagram of a shared directory management device according to an embodiment of the present disclosure.

FIG. 7 schematically shows a block diagram of an electronic device according to a shared directory management method according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood, however, that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for convenience of explanation, numerous specific details are set forth to provide a comprehensive understanding of the disclosed embodiments. It will be apparent, however, that one or more embodiments may be practiced without these specific details. Furthermore, in the following description, descriptions of well-known structures and techniques are omitted to avoid unnecessarily confusing the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. The terms "comprising," "comprising," and the like, as used herein, indicate the presence of stated features, steps, operations, and/or components but do not exclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. It should be noted that the terms used here should be interpreted to have meanings consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

Where an expression similar to "at least one of A, B, C, etc." is used, it should generally be interpreted in accordance with the meaning that a person skilled in the art generally understands the expression to mean (e.g., "having A, B and C "A system with at least one of" shall include, but is not limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or systems with A, B, C, etc. ).

Several block diagrams and/or flow diagrams are shown in the accompanying drawings. It will be understood that some blocks in the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus such that the instructions, when executed by the processor, create functions for implementing the functions illustrated in these block diagrams and/or flowcharts. /operating device. The technology of the present disclosure may be implemented in the form of hardware and/or software (including firmware, microcode, etc.). Additionally, the technology of the present disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon, and the computer program product may be used by or in conjunction with an instruction execution system.

In the technical solution of this disclosure, the collection, storage, use, processing, transmission, provision, disclosure and application of user personal information are in compliance with relevant laws and regulations, necessary confidentiality measures are taken, and do not violate Public order and good customs.

In the technical solution of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

Embodiments of the present disclosure provide a shared directory management method, device, electronic device, storage medium and program product, which can be used in the financial field or other fields. The method is suitable for execution in a computing device, and an operating system exists in the computing device. The method includes: configuring a management program in the operating system and installing the management program, and selecting the network sharing page in the file explorer to call and run the installation program after the installation is completed. Management program; among them, the management program includes the task scheduler, the task scheduler includes management tasks, and the management tasks are used to start the management program regularly; set the host user permissions of the management program, create the current shared directory and set the access permissions of other users, open the current Shared directory; after the current shared directory is shared, the management task is executed to close the current shared directory; after the current shared directory is closed, the management program is uninstalled.

Figure 1 schematically shows the system architecture of a shared directory management method and device according to an embodiment of the present disclosure. It should be noted that Figure 1 is only an example of a system architecture to which embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiments of the present disclosure cannot be used in other applications. Device, system, environment or scenario.

As shown in Figure 1, the system architecture 100 of the shared directory management method and apparatus according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is a medium used to provide communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

Users can use terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).

The terminal devices 101, 102, and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 105 may be a server that provides various services, such as a backend management server that provides support for websites browsed by users using the terminal devices 101, 102, and 103 (example only). The background management server can analyze and process the received user request and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the shared directory management method provided by the embodiment of the present disclosure can generally be executed by the server 105 . Correspondingly, the shared directory management device provided by the embodiment of the present disclosure may generally be installed in the server 105 . The shared directory management method provided by the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and/or the server 105. Correspondingly, the shared directory management apparatus provided by the embodiment of the present disclosure may also be provided in a server or server cluster that is different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks and servers in Figure 1 is only illustrative. Depending on implementation needs, there can be any number of end devices, networks, and servers.

The shared directory management method of the embodiment of the present disclosure will be described in detail based on the system architecture described in Figure 1 and through Figures 2 to 7 below.

Figure 2 schematically shows a flow chart of a shared directory management method according to an embodiment of the present disclosure.

In operation S210, configure a management program in the operating system and install the management program. By selecting the network sharing page in the file explorer, call and run the installed management program;

Among them, the management program includes a task scheduler, the task scheduler includes management tasks, and the management tasks are used to start the management program regularly.

Operation S220 is to set the host user permissions of the management program, create the current shared directory and set the access permissions of other users, and open the current shared directory.

In operation S230, after the current shared directory is shared, the management task is executed to close the current shared directory.

In operation S240, after closing the current shared directory, the management program is uninstalled.

Through the embodiments of the present disclosure, based on the shared directory management method, through convenient opening and closing of sharing, automatic clearing of time-limited sharing, automatic clearing of user permissions, clear authorized user permissions, information security risks are effectively solved, and safe and convenient The file sharing environment facilitates everyone to use shared directories safely, compliantly and conveniently, and reduces operating system resource overhead.

FIG. 3 schematically illustrates a flow chart of a process of installing and running a hypervisor according to an embodiment of the present disclosure.

As shown in Figure 3, in the embodiment of the present disclosure, in the above-mentioned operation S210, the management program is configured in the operating system, and after the management program is installed, the management program is called up by selecting the network sharing page in the file resource manager directory. Among them, the management program includes a task scheduler, the task scheduler includes management tasks, and the management tasks are used to start the management program regularly.

Specifically, click on the management program to install it. During the installation process, add registry entries to realize the option of adding a network sharing page in the right-click menu of the mouse; set the program parameter -reg and execute the management program.

Among them, when the program parameter is set to -M, the task scheduler is executed. The task scheduler includes management tasks, and the management tasks are used to start the management program regularly.

When the display management program installation is complete, the installation ends. Then call up the management program by selecting the network sharing page in the File Explorer directory.

Figure 4 schematically shows a flow chart of a process of opening a shared directory according to an embodiment of the present disclosure.

As shown in Figure 4, in the embodiment of the present disclosure, in the above-mentioned operation S220, the host user permissions of the management program are set, the current shared directory is created and the access permissions of other users are set, and the current shared directory is opened. Operations S221 to S224 may further be included.

In operation S221, it is determined whether the host user permission is set for the first time. If so, the host user permission is set to the permission information of the current host user; otherwise, the last set permission information is retained as the host user permission.

In operation S222, the creation instruction of the operating system is called to create the current shared directory.

In operation S223, the access instruction of the operating system is called to set the access permission information of other users.

In operation S224, the host user permission information and other users' access permission information are saved.

Specifically, the current directory is not shared. Select the My Network Sharing page to call up the management program. The authorization input items are automatically filled in with the authorized user name and permissions saved when sharing was last opened as the default reference value. If this directory For first-time use and there is no corresponding permission information, fill in the current host user name and full control permissions.

In order to make the program have good system applicability, the instructions of the operating system can be directly called to create the shared directory and authorize it.

In this embodiment, when the creation instruction of the operating system is called to create the current shared directory, the system management tool is used to obtain the first object, and the attributes of the first object are used to access the shared directory list generated in the computing device; traverse the computing device The generated shared directory list is compared with the directory name of the current shared directory until the directory name of the current shared directory is not repeated.

Specifically, use Windows WMI (system management tool) to obtain the object winmgmts (the first object), access the shared directory list generated by this machine, and generate the shared directory name based on the current directory name. However, because the name cannot be repeated, anti-conflict must be performed deal with. Traverse the shared directory list generated by this machine and compare the current shared directory name. If there is a conflict in the current shared directory name, add a serial number in parentheses at the end of the name, and compare again until there is no conflict.

When the host user is authorized successfully, use the operating system command icacls to implement access control authorization for other users. Save the currently authorized users and permissions as default reference values when sharing is enabled next time.

After completing the above steps, it will display that the current directory has been shared, the name of the current shared directory, access permissions, and a brief prompt on how to access the Xinchuang system.

Through the embodiments of the present disclosure, sharing can be started conveniently and efficiently, and authorized user permissions are clear. The sharing opening process is authorized accurately on demand, completely avoiding everyone, and effectively solving hidden information security risks.

In this embodiment, during the installation process of the management program, when the program parameter is set to -M, the task scheduler is executed. The task scheduler includes management tasks, where the management tasks are used to perform any of the following operations:

Call the task instructions of the operating system to perform management tasks in the task scheduler; run the task scheduler; start the management program regularly; or close the current shared directory.

In this example, closing the current shared directory includes: traversing the generated shared directory list in the computing device, comparing the difference between the sharing time of the generated shared directory and the sharing time of the current shared directory; The current shared directory with abnormal sharing time and time information will be closed, and the permission information of the current shared directory will be cleared.

Specifically, during the installation process, the management program executes the task scheduler of the operating system and the management tasks of the task scheduler by setting the parameter -M in the operating system. The task scheduler starts and runs this management program regularly (can be started multiple times a day by specifying time intervals)

In the management task, the object winmgmts (second object) is obtained through Windows WMI (system management tool), the shared directory list generated by the machine is traversed, and the properties and methods provided by the object are used to close the sharing function.

In the management task, the generated shared directory list is traversed, and the sharing time of the generated shared directory is compared with the time difference of the current shared directory. Current shared directories that have exceeded the time limit and have abnormal information are deleted one by one to close the sharing.

In this embodiment, closing the current shared directory also includes: calling a shutdown instruction of the operating system, using a system management tool to obtain the second object, and using the attributes of the second object to access the generated shared directory list and the current shared directory in the computing device. ; Traverse the generated shared directory list and the current shared directory in the computing device, and use the attributes of the second object to clear the permission information of the current shared directory.

Specifically, the object winmgmts (second object) is obtained through Windows WMI (system management tool), and the properties and methods provided by the object are used to traverse the generated shared directory list and the current shared directory in the local machine, and the currently existing shares are Clear the user permissions of the shared directory one by one and close the sharing one by one.

In this embodiment, by adjusting the parameters of the management program, the sharing time of the current shared directory is adjusted and the permission information of the current shared directory is cleared regularly. Among them, the parameters of the management program include: the duration of the current shared directory. If the current sharing time exceeds this time, the shared directory must be closed for cleaning (seconds); the start time of cleaning the current shared directory, which is the time when the shared directory is closed and cleared in the management task. Time; the management time of the current shared directory is the interval between execution of management tasks.

Through the embodiments of the present disclosure, the shared directory management program can be conveniently closed, and the scheduler can be efficiently run to perform shared directory management tasks. Automatically clear timeout sharing and user permissions to achieve a safe and convenient file sharing environment.

In this example, select the My Network Sharing page to call up the management program, enter the command h, call the operating system instruction command, and display the instructions for use of the management program, including function introduction, usage and precautions.

Figure 5 schematically shows a flow chart of shared directory management program uninstallation according to an embodiment of the present disclosure.

As shown in Figure 5, after closing the current shared directory, uninstalling the management program includes operations S241 to S243.

In operation S241, the network sharing page in the file explorer is deleted.

In operation S242, the management task in the task scheduler is deleted.

In operation S243, the generated shared directory list and the current shared directory in the computing device are cleared.

Through the embodiments of the present disclosure, usage and uninstallation are convenient and fast, and operating system resource overhead is reduced.

Specifically, select the My Network Sharing page to bring up the management program, remove the My Network Sharing item in the registry, clear the management tasks in the Task Scheduler in the operating system, and clear all shared directories on the machine.

In this example, after calling up the management program, you can also enter the command u to directly call the uninstall command of the operating system to complete the uninstallation of the management program.

Based on the above shared directory management method, the present disclosure also provides a shared directory management device. The device will be described in detail below with reference to FIG. 6 .

Figure 6 schematically shows a block diagram of a shared directory management device according to an embodiment of the present disclosure.

As shown in FIG. 6 , the shared directory management device 600 of this embodiment includes a program installation module 610 , a shared directory opening module 620 , a shared directory closing module 630 , and a program uninstalling module 640 .

The program installation module 610 is used to configure a management program in the operating system and install the management program. By selecting the network sharing page in the file resource manager, call and run the management program after the installation is completed; wherein, the management program The program includes a task scheduler, the task scheduler includes a management task, and the management task is used to start the management program regularly. In one embodiment, the program installation module 610 may be used to perform the operation S210 described above, which will not be described again here.

The shared directory opening module 620 is used to set the host user permissions of the management program, create the current shared directory and set the access permissions of other users, and open the current shared directory. In one embodiment, the shared directory opening module 620 may be used to perform the operation S220 described above, which will not be described again here.

The shared directory closing module 630 is configured to execute the management task to close the current shared directory after the current shared directory is shared. In one embodiment, the shared directory closing module 630 may be used to perform the operation S230 described above, which will not be described again here.

The program uninstall module 640 is used to uninstall the management program after closing the current shared directory. In one embodiment, the program unloading module 640 may be used to perform the operation S240 described above, which will not be described again here.

According to the embodiment of the present disclosure, any multiple modules in the program installation module 610, the shared directory opening module 620, the shared directory closing module 630 and the program uninstalling module 640 can be combined into one module to implement, or any one of the modules can be implemented by Split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the program installation module 610, the shared directory opening module 620, the shared directory closing module 630 and the program unloading module 640 may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA) ), programmable logic array (PLA), system-on-a-chip, system-on-substrate, system-on-package, application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuits. Implementation, or implementation in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the program installation module 610, the shared directory opening module 620, the shared directory closing module 630 and the program uninstalling module 640 can be at least partially implemented as a computer program module. When the computer program module is run, the corresponding function.

FIG. 7 schematically shows a block diagram of an electronic device according to a shared directory management method according to an embodiment of the present disclosure.

As shown in FIG. 7 , an electronic device 700 according to an embodiment of the present disclosure includes a processor 701 that can be loaded into a random access memory (RAM) 703 according to a program stored in a read-only memory (ROM) 702 or from a storage part 708 program to perform various appropriate actions and processes. Processor 701 may include, for example, a general-purpose microprocessor (eg, CPU), an instruction set processor and/or associated chipset, and/or a special-purpose microprocessor (eg, application specific integrated circuit (ASIC)), or the like. Processor 701 may also include onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present disclosure.

In the RAM 703, various programs and data required for the operation of the electronic device 700 are stored. The processor 701, ROM 702 and RAM 703 are connected to each other through a bus 704. The processor 701 performs various operations according to the method flow of the embodiment of the present disclosure by executing programs in the ROM 702 and/or RAM 703. It should be noted that the program may also be stored in one or more memories other than ROM 702 and RAM 703. The processor 701 may also perform various operations according to the method flow of embodiments of the present disclosure by executing programs stored in the one or more memories.

According to embodiments of the present disclosure, the electronic device 700 may further include an input/output (I/O) interface 705 that is also connected to the bus 704 . Electronic device 700 may also include one or more of the following components connected to I/O interface 705: an input portion 706 including a keyboard, mouse, etc.; including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and an output section 707 of speakers and the like; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem and the like. The communication section 1109 performs communication processing via a network such as the Internet. Driver 710 is also connected to I/O interface 705 as needed. Removable media 711, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage portion 708 as needed.

The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the device/device/system described in the above embodiments; it may also exist independently without being assembled into the device/system. in the device/system. The above computer-readable storage medium carries one or more programs. When the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, but is not limited to, portable computer disks, hard disks, random access memory (RAM), and read-only memory (ROM). , erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include one or more memories other than ROM 702 and/or RAM 703 and/or ROM 702 and RAM 703 described above.

Embodiments of the present disclosure also include a computer program product including a computer program containing program code for performing the method illustrated in the flowchart. When the computer program product is run in the computer system, the program code is used to cause the computer system to implement the method provided by the embodiment of the present disclosure.

When the computer program is executed by the processor 701, the above-described functions defined in the system/device of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the systems, devices, modules, units, etc. described above may be implemented by computer program modules.

In one embodiment, the computer program may rely on tangible storage media such as optical storage devices and magnetic storage devices. In another embodiment, the computer program can also be transmitted and distributed in the form of a signal on a network medium, and downloaded and installed through the communication part 709, and/or installed from the removable medium 711. The program code contained in the computer program can be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

In such embodiments, the computer program may be downloaded and installed from the network via communication portion 709 and/or installed from removable media 711 . When the computer program is executed by the processor 701, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the systems, devices, devices, modules, units, etc. described above may be implemented by computer program modules.

According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure may be written in any combination of one or more programming languages. Specifically, high-level procedural and/or object-oriented programming may be utilized. programming language, and/or assembly/machine language to implement these computational procedures. Programming languages include, but are not limited to, programming languages such as Java, C++, python, "C" language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In situations involving remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device, such as provided by an Internet service. (business comes via Internet connection).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logic functions that implement the specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block in the block diagram or flowchart illustration, and combinations of blocks in the block diagram or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or may be implemented by special purpose hardware-based systems that perform the specified functions or operations. Achieved by a combination of specialized hardware and computer instructions.

Those skilled in the art will understand that the features described in the various embodiments and/or claims of the present disclosure may be combined or/or combined in various ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, various combinations and/or combinations of features recited in the various embodiments and/or claims of the disclosure may be made without departing from the spirit and teachings of the disclosure. All such combinations and/or combinations fall within the scope of this disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although each embodiment is described separately above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and these substitutions and modifications should all fall within the scope of the present disclosure.

Claims (13)

1. A shared directory management method adapted to be executed in a computing device having an operating system present therein, the method comprising:

Configuring a management program in the operating system and installing the management program, and calling and operating the management program after the installation is completed by selecting a network sharing page in a file resource manager;

the management program comprises a task planning program, wherein the task planning program comprises a management task, and the management task is used for starting the management program at fixed time;

setting the host user authority of the management program, creating a current shared directory, setting the access authority of other users, and starting the current shared directory;

after the current shared directory completes sharing, the management task executes and closes the current shared directory;

and unloading the management program after closing the current shared directory.

2. The method of claim 1, wherein the setting the host user authority of the hypervisor, creating the current shared directory, and setting the access authority of other users, and opening the current shared directory comprises:

judging whether the host user permission is set for the first time, if so, setting the host user permission as permission information of the current host user; otherwise, the authority information set last time is reserved as the user authority of the host;

Calling a creation instruction of the operating system to create the current shared directory;

calling an access instruction of the operating system and setting access authority information of the other users;

and storing the authority information of the host user and the access authority information of the other users.

3. The shared directory management method of claim 2, wherein the invoking the operating system create instruction creates the current shared directory comprises:

obtaining a first object by using a system management tool, and accessing a generated shared directory list in the computing device by using the attribute of the first object;

and traversing the generated shared directory list in the computing equipment, and comparing the directory names of the current shared directory until the directory names of the current shared directory are not repeated.

4. The shared directory management method of claim 1, wherein the management task is to perform any one of:

invoking a task instruction of the operating system, and executing a management task in the task planning program;

running the task planning program;

starting the management program at fixed time; or alternatively

Closing the current shared directory;

Wherein said closing said current shared directory comprises:

traversing a list of generated shared directories in the computing device, comparing a difference between a shared time of the generated shared directory and a shared time of the current shared directory;

closing the current shared directory exceeding the sharing time and abnormal time information of the generated shared directory, and clearing the authority information of the current shared directory.

5. The method of claim 4, wherein closing the current shared directory further comprises:

invoking a closing instruction of the operating system, obtaining a second object by using a system management tool, and accessing a generated shared directory list and the current shared directory in the computing device by using the attribute of the second object;

traversing the generated shared directory list and the current shared directory in the computing equipment, and clearing the authority information of the current shared directory by utilizing the attribute of the second object.

6. The method according to claim 4, wherein the parameters of the management program are adjusted to adjust the sharing time of the current shared directory and to remove the authority information of the current shared directory at regular time.

7. The shared directory management method as claimed in claim 6, wherein the parameters of the management program include:

the method comprises the steps of storing the current shared directory, clearing the starting time of the current shared directory and the management time of the current shared directory.

8. The shared directory management method of claim 1, wherein the method further comprises:

and calling a use instruction of the operating system, and displaying a use instruction of the management program, wherein the use instruction comprises function introduction, a use method and notes.

9. The shared directory management method of claim 1, wherein, after closing the current shared directory, offloading the hypervisor comprises:

deleting the network sharing page in the file resource manager;

deleting the management task in the task planning program;

and clearing the generated shared directory list and the current shared directory in the computing device.

10. A shared directory management apparatus adapted to execute in a computing device, the computing device having an operating system present therein, the shared directory management apparatus comprising:

the program installation module is used for configuring a management program in the operating system and installing the management program, and calling and running the management program after the installation is completed by selecting a network sharing page in the file resource manager; the management program comprises a task planning program, wherein the task planning program comprises a management task, and the management task is used for starting the management program at fixed time;

The shared catalog opening module is used for setting the host user permission of the management program, creating a current shared catalog, setting the access permission of other users and opening the current shared catalog;

the shared catalog closing module is used for closing the current shared catalog after the current shared catalog is shared;

and the program unloading module is used for unloading the management program after closing the current shared directory.

11. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.

12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1 to 9.

13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 9.