JPH11338822A - Unix management file update system, computer constituting the system, computer readable medium recorded with update control program, and data recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable even a general user to easily and securely perform the maintenance of a UNIX management file. SOLUTION: The management data of the UNIX management file are registered on registration lists 22, 23, 24... of RDB 2 so as to update the management data on these registration lists from a user interface 3. When the management data on the registration list are updated, an identifier S corresponding to an updated item is outputted from an update activation processing part provided in an RDBMS 21. An update processing part 11 installed in a UNIX server 1 reads a working procedure corresponding to the identifier S out of a working procedure file and reads data out of the prescribed registration list instructed by that working procedure. Afterwards, the prescribed UNIX management file (one or plural UNIX management files to be reflected with the data updated on the RDB 2) instructed by the working procedure is updated.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a UNIX management file update system, a computer constituting the system, a computer-readable medium storing an update control program, and a data recording medium.
The present invention relates to a UNIX management file update system for updating an / etc / passwd file and the like.

[0002]

2. Description of the Related Art In an open system employing UNIX (trademark) as an OS (operating system),
A superuser is defined as a system administrator, and this superuser is required to execute files necessary for UNIX operation (hereinafter referred to as “U”).
NIX management file).

There are many types of UNIX management files, one example of which is shown in FIG. FIG. 8 (a) shows / etc /
A password file, which is a login name and its corresponding encrypted password, user ID, and group I
D and a home directory at the time of login are designated. FIG. 7B shows the / etc / services file. The port number corresponding to the network service name is specified. FIG. 7C shows / etc / inet.
d. It is a conf file. The startup program corresponding to the network service name is specified. here,
Each piece of data (such as the above-mentioned user ID and network service name) constituting the UNIX management data will be referred to as management data.

[0004]

However, in the above-mentioned conventional example, a plurality of UNIX management files often include the same management data. For example, a super-user is required to have a network of / etc / services file. To update the service name, use / etc / in
etd. The network service name of the conf file must also be updated to match each UNIX management file, and the maintenance work is complicated.

[0005] In addition, the super user must directly rewrite the contents of the UNIX management file using a text editor.
There is a possibility that an erroneous operation such as adding a line that does not conform to a predetermined format may be performed. In this case, the OS may not be booted correctly. Therefore, updating the file required a lot of expertise.

[0006] Further, the updating of the UNIX management file is a privilege particularly recognized when a super user logs in with a correct ID and password. However, if the password is stolen by another person, the UNIX management file is destroyed and the system is destroyed. May not start. vice versa,
Since this authority is given only to the super user, for example, a new user cannot perform an operation such as registering his / her own user ID by himself, and requests the super user to update the UNIX management file. Because of the need to obtain it, the burden on the superuser was heavy.

[0007]

An object of the present invention is to provide a UNIX management file updating system and the like which solves the disadvantages of the prior art and in particular, makes it possible for ordinary users to easily and safely maintain a UNIX management file. The purpose is to do.

[0008]

In order to achieve the above object, in the system according to the first aspect, there is provided a relational database having a registration table in which management data contained in a UNIX management file is registered, and a method of accessing and registering the relational database. It has a user interface that can update the management data of the table, and an update activation processing unit that outputs an identifier corresponding to the update item when the management data of the registration table is updated. Also, a work procedure file describing a registration table to be referred to for each identifier and one or a plurality of UNIX management files to be updated, and a work corresponding to the identifier when the identifier is output from the update activation processing unit. An update processing unit for reading a procedure from a work procedure file and updating a predetermined UNIX management file with reference to a predetermined registration table in accordance with the work procedure is provided.

[0009] The computer according to claim 2 is UNIX.
A relational database comprising a registration table in which the management data included in the management file is registered, and receiving an update of the management data in the registration table from an external user interface;
An update start processing unit that outputs an identifier corresponding to the update item when the management data of the registration table is updated, and causes the update processing unit to update a predetermined UNIX management file corresponding to the identifier. I am taking it.

[0010] The computer according to claim 3 is a UNIX computer.
A computer having a file update function of updating a UNIX management file according to an update item when a registration table of a relational database in which management data of a management file is registered is updated. The system includes a work procedure file in which a database registration table and one or more UNIX management files to be updated are described, and a procedure reference processing unit that reads a work procedure corresponding to an update item from the work procedure file. Also, a registration table reference processing unit that reads a registration table of a relational database instructed in the read work procedure, and a registration table read processing unit that reads one or more UNIX management files instructed in the work procedure. An update execution unit that updates based on management data is provided.

According to a fourth aspect of the present invention, when a registration table of a relational database in which management data of a UNIX management file is registered is updated, an update item determination process of determining the update item is performed. An update control program for causing a computer to execute an update starting process for outputting an identifier to an update processing unit and updating one or more UNIX management files corresponding to the identifier is recorded. .

According to a fifth aspect of the present invention, when an identifier is output from the update start processing unit, a work procedure corresponding to the identifier is read from a work procedure file, and registered in a relational database according to the read work procedure. Registration table reference processing for reading the registered registration table,
An update control program for causing a computer to execute an update process for updating one or more predetermined UNIX management files specified by the work procedure based on the read registration table is recorded.

According to a sixth aspect of the present invention, in the medium, a plurality of identifier data corresponding to the identifier output by the update start processing unit are recorded, and a predetermined registration table of a relational database to be referred to when updating the UNIX management file is stored. The configuration is such that work procedure data including information relating to one or more predetermined UNIX management files to be updated is recorded in association with each identifier data. This aims to achieve the above-mentioned object.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to FIGS.

FIG. 1 is a block diagram showing the configuration of a UNIX management file update system. The registration tables 22 and 23 register management data contained in the UNIX management file.
, And a relational database 2 (hereinafter abbreviated as RDB2 as appropriate) having access to the relational database 2 and registration tables 22, 23, 24,
, And a plurality of user interfaces 3, 3,... Capable of updating the management data, and an update activation for outputting an identifier S corresponding to the update item when the management data of the registration tables 22, 23, 24,. And a processing unit. In the present embodiment, the update activation processing unit is included in a relational database management system 21 (hereinafter, abbreviated as RDBMS 21). The registration tables 22, 23, 24,... To be referred to for each identifier S, and one or more UNIX management files 13, 14, 15,.
.. And an operation procedure corresponding to the identifier S when the identifier S is output from the update start-up processing unit, are read from the operation procedure file 12 and predetermined registration tables 22, 23, , And an update processing unit 11 that updates predetermined UNIX management files 13, 14, 15,.

More specifically, in the present embodiment, the system connects a computer functioning as a UNIX server 1, a computer functioning an RDB 2, and a plurality of computers having a user interface 3 to a network 4. Consisting of

Accordingly, looking at the configuration of the system for each computer, the computer functioning as the RDB 2 has registration tables 22, 23, 24,... In which management data contained in the UNIX management file is registered. From 3, 3, ..., the registration tables 22, 23, 2
, And when the management data of the registration tables 22, 23, 24,... Are updated, the identifier S corresponding to the update item is output to the update processing unit 11. A predetermined U corresponding to the identifier S
And an update start processing unit for updating the NIX management files 13, 14, 15,... R included in RDB2
The DBMS 21 is a general one such as ORACLE (trademark), and the update start processing unit is realized by an update control program described in SQL or the like. in this case,
This update control program includes registration tables 22, 23, 24,
.. Are updated, an update item determination process for determining the update item, and an identifier S corresponding to the determined update item is output to the update processing unit 11 and one or more UNIX management files corresponding to the identifier S May be read from a medium recording a program for causing a computer to execute the update activation process for performing the update.

In this embodiment, the service registration table 22, the group registration table 23, and the user registration table 2
4 is prepared on a storage medium. FIG.
(A) is a configuration diagram of the service registration table 22, in which a port number and an inetd startup program name are registered for each service name. FIG. 2B is a configuration diagram of the group registration table 23, in which a group ID and an additional description (comment) are registered for each belonging group. FIG. 2C is a configuration diagram of the user registration table 24, in which a name, a user ID, and a belonging group are registered for each login name. Here, the item of the belonging group in the user registration table 24 and the item of the belonging group in the group registration table 23 are linked. It is also assumed that a registration table including other management data is prepared in the RDB 2 in advance (not shown).

On the other hand, the computer functioning as the UNIX server 1 is a workstation employing UNIX as the OS. When the registration tables 22, 23, 24,... UNIX management files 13, 14, 15, ...
It has a file update function for updating. For this reason,
The registration tables 22, 23, 24,... To be referred to in accordance with the update item indicated by the identifier S, and one or more UNs to be updated
IX management files 13, 14, 15,... Are described, and a procedure reference processing unit for reading a work procedure corresponding to an update item from the work procedure file 12. In FIG. 1, the procedure reference processing unit is included in the update processing unit 11. Also, a registration table reference processing unit that reads the registration tables 22, 23, 24,... Instructed in the read work procedure, and one or a plurality of U
., The NIX management files 13, 14, 15,... Are read by the registration table reference processing unit.
And an update execution unit for updating based on the management data of. Here, the registration table reference processing unit and the update execution unit are also included in the update processing unit 11. The update processing unit 11 operates with the same level of authority as a conventional super user.

In this embodiment, the update processing unit 11
This is realized by a CPU (not shown) executing an update control program described in C language or the like. The update control program is, when the identifier S is output from the update activation processing unit, a procedure reference process for reading the work procedure corresponding to the identifier S from the work procedure file 12, and is registered in the relational database 2 according to the read work procedure. The registration table reference processing for reading the predetermined registration table and the update processing for updating one or more predetermined UNIX management files 13, 14, 15,... Designated by the work procedure based on the read management data are performed by the computer. The program may be a program read from a medium on which a program to be executed is recorded.

The work procedure file 12 is provided in a predetermined storage area. FIG. 3 is a schematic configuration diagram of a work procedure file. The registration table data 12b to be referred to corresponding to each identifier data 12a and the UNIX to be updated
The path data 12c of the management file and other necessary data 12d required for the update processing are registered. here,
The work procedure file 12 records a plurality of pieces of identifier data 12a corresponding to the identifier S, a registration table 12b to be referred to when updating the UNIX management file, and one or more predetermined UNIX management files 12c to be updated. Work procedure data including information on each identifier data 1
The data may be read from a computer-readable medium recorded in association with each 2a.

The UNIX management file includes all conventional general files, such as the / etc / passwd file 13 and / etc / passwd file 13 illustrated as conventional examples.
services file 14 or / etc / inetd. c
An onf file 15 is also included.

In the present embodiment, the user interface 3 is a WWW (World Wide Web) browser, and can be used even by a user who does not have the authority of a super user. By specifying the URL from this browser, the RDBMS 21
, And can refer to the items of the registration tables 22, 23, 24,. Here, the item for which the RDBMS 21 is requested to output is specified in the HTML file for each URL, and the users who can access by the authentication for each URL are individually restricted. As the restriction here, it is possible to set a flexible restriction that is more relaxed than the conventional super user title.

The network 4 can adopt the Internet, an in-house LAN, an intranet, or the like.

Next, the operation of this embodiment will be described.

The user selects a predetermined URL from which an item to be updated can be edited and inputs the URL to the user interface 3. As a result, the HTML corresponding to the specified URL is activated, and after connecting to the RDBMS 21, a part of predetermined registration tables 22, 23, 24,... Will be displayed on the terminal and will be editable. The user instructs the RDBMS 21 to update after adding, modifying or deleting the target item. R receiving an update command from the user interface 3
The DBMS 21 registers the registration tables 22 and 2 including the changed items.
Update all of 3, 24,. For example, when the user calls the user registration table 24 and updates the "affiliation group", in addition to the update of the user registration table 24, the "affiliation group" of the group registration table 23 linked thereto is also updated. . The above is provided by the conventional general functions of the RDBMS. When the RDBMS 21 receives the update of the registration table, the update start processing unit in the RDBMS 21 starts.

FIG. 4 is a flowchart showing the operation of the update start processing unit. The activated update activation processing unit first activates
The updated item is determined (S1). In this embodiment,
The update item is determined by determining the updated registration table. Subsequently, the update activation processing unit outputs the identifier S corresponding to the update item to the update processing unit 11. In the present embodiment, a different identifier S is output according to the type of the updated registration table.

When the identifier S is output from the update start processing unit, the update processing unit 11 starts. FIG. 5 is a flowchart illustrating the operation of the update processing unit 11. The update processing unit 11 refers to the work procedure file 12 and registers a reference table 12b to be referenced and a UNI to be updated, which are registered in association with the identifier S received from the update start processing unit.
The path 12c of the X management file and other information necessary for updating are read (S11).

Hereinafter, a description will be given along a specific example. It is assumed that the user updates the user registration table 24 from the user interface 3, and at this time, “1” is output as the identifier S from the update activation processing unit in the RDBMS 21. Hereinafter, the update processing unit 11 receiving this identifier "1"
The operation of updating the c / passwd file will be described.
The update processing unit 11 that has received the identifier “1” refers to the work procedure file 12 and refers to the “user registration table” and “group registration table” as the registration tables 12b to be referred to and associated with the identifier “1”. And other information. Also, as the UNIX management file 12c to be updated, "/ etc
/ Passwd ". Further, other necessary information 12d such as a reference procedure is obtained (S11).

Subsequently, the / etc / passwd file is locked and read / write by others is prohibited (S
12). After that, authentication is performed with the RDBMS 21,
A connection with the RDBMS 21 is established (S13).

Here, various authentication methods are conceivable. R
When the DBMS 21 is authenticated by the update processing unit 11, the update processing unit 11 transmits the authentication code registered in the RDBMS 21 in advance, the terminal ID of the connection source computer including the RDBMS 21, or the network address included in the communication data of the connected RDBMS 21. RDBM based on etc.
The authentication of S may be performed. The update processing unit 11 uses the authentication function normally provided in the RDBMS 21 and
The authentication of the DBMS 21 may be received.

The update processing unit 11, which has completed the authentication and established the connection with the RDBMS 21, first reads all the management data from the updated user registration table 24 according to the reference procedure (S14). Subsequently, the updated group registration table 23 is searched using the item of “affiliation group” of the user registration table 24 that has just been read as a key, and data is read (S15).
Then, the user I in the user registration table 24 read out earlier
D and the group ID of the group registration table 23 just read
(S16). Subsequently, the update processing unit 11 searches and reads other management data necessary for forming the / etc / passwd file from another registration table (not shown). At this time, for example, a search is performed using the user ID as a key (S17). Thus, / etc / pas
After acquiring the management data necessary for generating the swd file, the / etc / passwd file is updated (S1).
8). Then, the lock of the / etc / passwd file is released (S19), and the process ends.

Next, another operation example will be described with reference to FIG. RD when the user updates the service registration table 22
It is assumed that the update start processing unit in the BMS 21 outputs the identifier “2”. The update processing unit 11 stores the work procedure file 1
2, the “service registration table” corresponding to the identifier “2” is obtained as the registration table 12b to be referred. Also, “/ etc /
services "" /etc/inetd.con
f ”and the like. In addition, other necessary information 12 such as work procedure
Obtain d. Then, a connection with the RDBMS 21 is established in the same manner as described above, and all the management data in the service registration table 22 is read. Then, based on the instructed work procedure, FIG.
, The / etc / services file is updated based on the items of “service name” and “port number”, and at the same time, based on the items of “service name” and “inetd start program”, the / etc / inetd. c
The onf file can also be updated.

Next, FIG. 7 shows an extended example of this embodiment.
As shown in FIG. 7, a plurality of RDBMSs and a plurality of UNs
IX server can be arbitrarily connected via a network. For example, user registration is managed by the human resources department, and each UNIX
An operation form in which server host registration is managed by the computer management section is also possible.

As described above, according to the present embodiment, a general user can update the data of the UNIX management file with respect to the registration table of the RDBMS, and the superuser authority update processing unit is updated by updating the registration table. Is started, and the contents of the update to the registration table are reflected in one or more UNIX management files. For this reason, the burden of file maintenance on the super user can be reduced, and the present system can be realized without making any changes to the existing OS.

Further, since it becomes possible to input the update items via a dedicated user interface, it is not necessary to directly modify the file using a text editor as in the conventional case, and the file format is broken and the OS Can be prevented from being unable to boot, and the security of file maintenance can be ensured. In particular, RD
The input items (character type, number of characters, etc.) can be restricted by checking the input items by the general function of BMS, so that even general users without expertise can safely and easily update the management data. Can be.

Further, utilizing the general functions of the RDBMS,
Many general users can update the management data from each user interface via the network, and the management data that can be updated for each connected user can be restricted by the authentication function of the RDBMS. It is. Specifically, the right to read, change, delete, and the like can be set freely for each user. For this reason, it is possible to realize a highly safe UNIX management data update system that has high adaptability to the UNIX file management system and provides more flexible file operation authority.

Further, a user interface, an RDBMS
And the update processing unit are separate processes, and can exchange data and instructions by an inter-process communication procedure, but take a configuration of a distributed management system which is not restricted by a physical configuration of a computer or a network. It is possible to construct an optimal management system according to the business form. In particular, RDBM
Since the registration table managed by S can have an optional comment column, it is possible to add and manage a comment sentence even to an item having no comment column as the format of the UNIX management file. , User ID, etc.
It is also possible to integrally manage the management data of NIX and other administrative personal information.

Here, the present invention is not limited to the above embodiment. The UNIX server 1, RDB 2 and user interface 3 do not necessarily need to be provided on separate computers, and the UNIX server 1, RD
B2, functions as a user interface may be included in any combination. The registration table attached to the RDBMS may be created by inputting management data by an operator, or may be automatically generated by referring to a UNIX management file by program processing. The update activation processing unit may be a process independent of the RDBMS, and may be any unit that detects an update of the registration table by the user interface and outputs an identifier corresponding to the update item. The reference processing of the registration table at the time of updating the UNIX management file may be a reference processing of reading only a part of the registration table, instead of referring to the entire registration table as in the above embodiment.

[0040]

The present invention is constructed and functions as described above. According to this, a general user can update the data of the UNIX management file with respect to the registration table of the RDBMS, and The update activates the superuser authority update processing unit, and reflects the contents of the update to the registration table in one or more UNIX management files. For this reason, the burden of file maintenance on the super user can be reduced, and the present system can be realized without making any changes to the existing OS.

Further, since it becomes possible to input the update items through a dedicated user interface, there is no need to directly modify the file using a text editor as in the conventional case, and the file format is broken and the OS Can be prevented from being unable to boot, and the security of file maintenance can be ensured. In particular, RD
The input items (character type, number of characters, etc.) can be restricted by checking the input items by the general function of BMS, so that even general users without expertise can safely and easily update the management data. Can be.

Further, utilizing the general functions of the RDBMS,
Many general users can update the management data from each user interface via the network, and the management data that can be updated for each connected user can be restricted by the authentication function of the RDBMS. It is. Specifically, the right to read, change, delete, and the like can be set freely for each user. For this reason, it is possible to realize a highly safe UNIX management data update system that has high adaptability to the UNIX file management system and provides more flexible file operation authority.

Also, user interface, RDBMS
And the update processing unit are separate processes, and can exchange data and instructions by an inter-process communication procedure, but take a configuration of a distributed management system which is not restricted by a physical configuration of a computer or a network. It is possible to construct an optimal management system according to the business form. In particular, RDBM
Since the registration table managed by S can have an optional comment column, it is possible to add and manage a comment sentence even to an item having no comment column as the format of the UNIX management file. , User ID, etc.
An unprecedented UNIX management file update system capable of integrally managing NIX management data and other administrative personal information, etc., and a computer and update control program constituting the system. A computer readable medium and a data recording medium can be provided.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a UNIX management file update system according to the present invention.

2 is an example of a registration table managed by the RDBMS of FIG. 1; FIG. 2 (a) is a service registration table, FIG. 2 (b) is a group registration table, and FIG. 2 (c) is a configuration of a user registration table; Is shown.

FIG. 3 is a configuration diagram of a work procedure file shown in FIG. 1;

FIG. 4 is a flowchart illustrating an update activation process.

FIG. 5 is a flowchart showing an update process.

FIG. 6 is an explanatory diagram for explaining an example of the operation of the embodiment in FIG. 1;

FIG. 7 is a configuration diagram illustrating an extended example of the embodiment of FIG. 1;

FIG. 8 is an explanatory diagram showing an example of a conventional general UNIX management file. FIG. 8A shows an / etc / passwd file, and FIG. 8B shows / etc / service.
s file, and FIG. 8C shows / etc / inet.
d. Indicates a conf file.

[Explanation of symbols]

REFERENCE SIGNS LIST 1 UNIX server (computer) 2 relational database (computer) 3 user interface 4 network 11 superuser proxy program (update processing unit) 12 work procedure file 13, 14, 15 UNIX management file 21 RDBMS (update start processing unit) 22, 23 , 24 registration table S update item identifier N authentication S1 update item determination process S2 update activation process S11 procedure reference processing unit (procedure reference process) S14, S15, S16, S17 registration table reference processing unit (registration table reference process) S18 Update execution Department (update process)

Claims (6)

[Claims] 1. A relational database having a registration table in which management data included in a UNIX management file is registered, a user interface capable of accessing the relational database and updating the management data of the registration table, and a management data of the registration table An update activation processing unit that outputs an identifier corresponding to the update item when is updated,
A work procedure file describing a registration table to be referred to for each identifier and one or more UNIX management files to be updated, and a work corresponding to the identifier when the identifier is output from the update activation processing unit. An update processing unit that reads a procedure from the work procedure file and updates a predetermined UNIX management file with reference to a predetermined registration table in accordance with the work procedure. 2. A relational database having a registration table in which management data included in a UNIX management file is registered and receiving an update of the management data in the registration table from an external user interface, and when the management data in the registration table is updated And an update start processing unit that outputs an identifier corresponding to the update item and causes the update processing unit to update a predetermined UNIX management file corresponding to the identifier. 3. A computer having a file update function of updating a UNIX management file according to an update item when a registration table of a relational database in which management data of the UNIX management file is registered is updated. A registration table of the relational database to be referred to according to an item and one or more UNIs to be updated
A work procedure file describing an X management file, a procedure reference processing unit for reading a work procedure corresponding to the update item from the work procedure file, and a registration for reading a registration table of the relational database instructed by the read work procedure A table reference processing unit; and an update execution unit configured to update one or a plurality of UNIX management files specified in the work procedure based on management data of the registration table read by the registration table reference processing unit. Features computer. 4. An update item determination process for determining an update item when a registration table of a relational database in which management data of a UNIX management file is registered is updated,
An update control program for causing a computer to execute an update start process for outputting an identifier corresponding to the determined update item to the update processing unit and updating one or more UNIX management files corresponding to the identifier is recorded. Computer readable medium. 5. A procedure reference process for reading a work procedure corresponding to an identifier from a work procedure file when an identifier is output from an update activation processing unit, and a predetermined registration table registered in a relational database according to the read work procedure. And a plurality of predetermined UNs specified by the work procedure based on the read registration table.
A computer-readable medium recording an update control program for causing a computer to execute an update process for updating an IX management file. 6. A plurality of identifier data corresponding to identifiers output by the update activation processing unit, and a predetermined registration table of a relational database to be referred to when updating a UNIX management file, and one or more to be updated. A computer-readable data recording medium which records operation procedure data including information on a predetermined UNIX management file in association with each of the identifier data.