JP3329490B2 - Information processing system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file creation method for an information processing device such as a personal computer, and more particularly, to a file storage device of an information processing device shared by a plurality of users via a network. The present invention relates to an information processing system suitable for creating a file from a device.

[0002]

2. Description of the Related Art Prior to the spread of personal computers (hereinafter referred to as personal computers), user's program files, data files, and the like were stored in a storage device of each personal computer. As personal computers have become widespread, a method of storing program files, data files, and the like of these users in a single large-capacity storage device and sharing data with each personal computer user has come to be used. According to this, each personal computer can easily access data larger than the capacity of the storage device provided in the personal computer. In such a system, a computer called a file server and a plurality of personal computers called clients are generally connected via a network. Then, a file on a storage device (server storage device) provided in the file server can be accessed and used from the client personal computer. Here, a user can issue an operating system (hereinafter referred to as OS) command to a file on the server storage device in the same manner as accessing a file on the local storage device of the client personal computer. I have. Access to files on the server storage device from application software (hereinafter referred to as AP) can be performed in the same manner as access to files on the local storage device of the client personal computer.

FIG. 2 shows a conventional example of a system in which a client personal computer can access a server storage device as described above.

[0006] In FIG. 2, a file server 1 is connected to a network line 5, and a server storage device 2 is connected to the file server 1. Network 5
Is connected to a client personal computer 3, and a client storage device 4 is connected to the client personal computer 3.

The file server 1 has a network OS
14 and network driver 13, network A
P15 is mounted. The client PC 3 includes an AP 30, an OS command 31, a redirector 32,
A network driver 33, a client OS 34, and a client AP 35 are mounted.

[0006] The network driver 13 is a driver for connecting the file server 1 and the network line 5.

The network OS 14 is an OS used in an online system of a very small keyboard for connecting several PCs to about a dozen PCs via a LAN and performing processing.
It is.

[0008] The AP 15 is an AP on a server, which can be commonly accessed by each client.

The AP and OS command 31 issue a system call (also called a function call) such as a file input / output request.

A redirector 32 (also called a client shell) receives a request issued from an AP or OS command 31. Then, the program determines whether the request is a request to be processed in the file server or a request to be processed in the client 3.

The network driver 33 is a driver for connecting the client 3 and the network line 5.

The OS 34 controls the client 3
S.

The AP 30 is an AP used by a client.
It is.

Next, the operation of the conventional system will be described.

When a system call is issued from the AP or OS command 31, it is determined by the program of the redirector 32 whether it should be processed by the file server or the client 3.

If the request is the former, the redirector 32 sends the request to the network driver 33, the network 5,
Network O via the network driver 13
A process is requested to S14. If the request is the latter, the redirector 32 sends the OS 34 (O
Request processing to S).

On the other hand, the files on the file server 1 are:
Access from a plurality of client personal computers 3 is possible. For this reason, an access right can be set such as whether access from another user's client personal computer 3 or use by a plurality of users is allowed. This is called file attribute setting. These attributes are added to the file in a form that extends the attributes of the file created in the storage device 4 of the client. Hereinafter, the attribute of the file on the storage device 2 will be referred to as an extended attribute with respect to the attribute of the file on the storage device 4. These attributes are set when creating the file.
Can be specified by the user.

Such attributes include:
For example, "read only", "hidden files"
There are “archive files” and “system files”. The extended attributes include “shared file”, “copy prohibited”, “delete prohibited”, “name change prohibited”, and the like.

The case where these attributes are set will be described below.

A file having "read only" as an attribute is not erased or written by a user.

A file having "hidden file" as an attribute is not displayed when the user displays the file name of a file in the directory.

Further, there is a command for backing up only files whose archive bit is "1" without backing up all files when backing up files. The archive bit is set to “1” for a file having “archive file” as an attribute.

A file having "system file" as an attribute cannot be accessed by a normal system call.

A file having "shared file" as an attribute is simultaneously referred to by a plurality of users.

A file having "copy prohibited" as an attribute is not copied by the user.

A file having "deletion prohibited" as an attribute is not deleted by the user.

A file having an attribute "rename prohibited" is not renamed by the user.

Client OS 34 and Network O
In S14, an attribute can be set by issuing a system call for changing the attribute.

For the network OS as described above, for example, “Interface” (19
March 1991) pp. 141-146.

[0030]

As described above, a file on a file server can be shared by a plurality of users by using attributes and extended attributes. However, these extended attributes are not supported by the commands of the client OS for the AP and the stand-alone. For this reason, after creating a file on the file server,
There is a problem that it is necessary to set an extended attribute using another command provided by S. In particular, when a plurality of files are created in different directories, it is necessary to set extended attributes for each directory. Therefore, in such a case, there has been a problem that it takes time to set the extended attribute and an operation error occurs.

An object of the present invention is to provide an information processing system capable of easily setting attributes without changing a conventional OS command and a file creation method using an AP.

[0032]

According to the present invention, a program or data that can be accessed by a plurality of users and an attribute indicating an access right of each user to the program or data are provided according to the present invention. In an information processing system including a file storage device that stores a file having at least a file creation request unit that generates a request for creating a file,
Attribute input means for inputting an attribute specified from the outside, attribute storage means for storing the attribute input by the input means, and when a file creation request is issued by the file creation request means, the attribute stored in the storage means is read. Add
File creation means for creating the requested file.

The attributes can be input prior to the generation of the file creation request.

Further, in a system in which a client terminal for inputting / outputting data and a server device having files and applications shared by the client are connected by a network line, the server can be accessed by a plurality of users. A first file storage device for storing a file having at least a program or data and an attribute indicating an access right of each user to the program or data, and a file for creating a file to be stored in the first file storage device First file creation request means for generating a request, and first file creation for creating a requested file by adding a designated attribute when a first file creation request is issued by the first file creation request means. Means may be provided. The client has an attribute input unit for inputting an attribute specified from the outside, an attribute storage unit for storing the attribute input by the input unit, and a request for creating a file to be stored in the first file storage device. And a activating means for activating the first file creating means by adding the stored attribute when the second file creating request is issued.

Further, there is provided a means for generating an interrupt when the second file creation request means is generated, and the first file creation means can be activated at the interruption.

Further, there is provided means for changing the interrupt vector address of the system call, and the activating means can activate the first file creating means using the changed vector address.

Further, when the first file creator started to create the file, it may have a means for restoring the changed interrupt vector address of the system call to the address before the change.

Further, the client stores a file having at least a program or data accessible from a plurality of users and an attribute indicating an access right of each user to the program or data. The second file creation requesting means further generates a request for creating a file to be stored in the second file storage device, and when the second file creation requesting means is issued, the first file storage requesting means A determining unit that determines whether the request is for creating a file to be stored in the device or a request for creating a file to be stored in the second file storage device; If it is determined that the request is for creating a file to be stored in the file storage device, the stored By adding Ribyuto, it may be provided with a second file creating means for creating the requested file in the second file storage device.

Further, there is provided a means for generating an interrupt when the second file creation requesting means is generated. In the interruption, determination is made and creation of a file by the second file creation means or activation of the first file creation means, Can also be performed.

[0040]

The user inputs desired attributes (including extended attributes) by the attribute input means prior to the creation of a file by the command of the client OS or the AP. The input attribute is stored by attribute storing means for storing the attribute. Next, when a file creation request is issued by a command of the client OS or an AP, it is detected whether the file creation request is for the file server or the client OS is for creation. When a creation request to the file server is detected, this request to the file server is issued by the file creation request means. When a file creation request is issued, a file is created by the file creation unit using the attribute stored in the storage unit as an attribute. This eliminates the need to set extended attributes, which was conventionally required for each directory when creating a file.

[0041]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of a system using the file creation method of the present invention. 2, the file server 1 is connected to the network line 5, and the server storage device 2 is connected to the file server 1, as in FIG. Also, the network 5 includes:
A client personal computer 3 is connected, and a client storage device 4 is connected to the client personal computer 3.

The file server 1 has a network OS
14 and network driver 13, network A
P15 is mounted.

The client PC 3 has an AP and an OS
Command 31, redirector 32, network driver 33, client OS 34, client AP3
0, a file control program 35 is installed.
Compared with the conventional example shown in FIG. 2, the feature of this embodiment is that the client personal computer 3
Is added.

The network driver 13 is a driver for connecting the file server 1 and the network line 5.

The network OS 14 is an OS used in an on-line system for a very small keyboard for connecting several PCs to about a dozen PCs via a LAN and performing processing.
It is.

The AP 15 is an AP on the server and can be commonly accessed by each client.

The AP / OS command 31 issues a system call (also called a function call) such as a file input / output request.

The redirector 32 (also called a client shell) receives a request issued from the AP or OS command 31. Then, the program determines whether the request is a request to be processed in the file server or a request to be processed in the client 3.

The network driver 33 is a driver for connecting the client 3 and the network line 5.

The OS 34 controls the client 3
S.

The AP 30 is an AP used by the client.
It is.

The file control program 35 comprises the elements shown in FIG. That is, the file control program 35 is roughly divided into the initialization routine 10
0, an interrupt processing routine 200, and an end routine 400.

In the initialization routine 100, an attribute is input (101), and the input attribute is stored (102). Also, the system call interrupt vector address pointing to the interrupt processing routine of the redirector 32 is stored and rewritten to the entry address of the interrupt processing routine (103). Then, a process for making the interrupt processing routine resident is performed (104).

In the interrupt processing routine 200, AP, O
It is determined whether a system call such as a file input / output request issued from the S command 31 is a file creation request to the file server 1 (201). If the result of the determination is that the system call is a file creation request to the file server 1,
By specifying the attribute stored in step 2, the network OS 14 is requested to create a file (202). If the result of the determination is that the request is not a file creation request to the file server 1, the system call issued from the AP and OS command 31 is passed as it is to the redirector 32 (203) and processed by the redirector as before. (2
04).

In the end routine 400, the system call interrupt vector address changed in 103 of the initialization routine 100 is restored to the original value (address of the redirector interrupt processing routine) (401). In addition, the file control program 35 ends, and the memory is released (402).

FIGS. 3 and 4 are examples of flowcharts showing the operation of the file control program 35 in one embodiment of the present invention.

FIG. 3 shows an initialization routine of the file control program 35, which is started by a user or another program.

When the initialization routine is started, first,
Acquire the input attribute (Step 10
1). The file control program 35 may request the user to input this attribute.
Further, when the file control program 35 is started, the file control program 35 may be passed as a parameter. As an attribute setting method, for example, a password of a user who can access the created file may be set.

As a method for obtaining the above attributes,
FIG. 9 shows an example of an input request screen when the file control program 35 makes an input request to the user.

In FIG. 9A, [Attribute]
Is set when a file is created on the storage device 4 and the storage device 2. [Extended attribute] is specified only when a file is created on the storage device 2. If the “AP setting value” is specified, A
On / off information predetermined for each P is set.

Next, the acquired attributes are stored in a memory (step 102).

For example, the attribute specified on the input screen shown in FIG. 9A is first stored in bits as shown in FIG. 9B. In FIG. 9B, two bits are assigned to each item of [DOS attribute] and one bit is assigned to each item of [extended attribute] in FIG. 9A. O for each item of [Attribute]
“01” is assigned to N, “00” is assigned to OFF, and “10” is assigned to the AP set value. For each item of [extended attribute], "1" for ON, OF
“0” is assigned to F. (When the AP is started as described later, “0” or “1” is added to the AP set value.
Assign In this way, 8-bit attribute information is generated. In step 103, the system call interrupt vector address indicating the interrupt processing routine of the redirector 32 is obtained from the memory and stored in another memory address. Along with this processing, the vector address is rewritten so as to indicate the entry address of the interrupt processing routine 200 in the file control program 35.

Finally, of the file control program 35, at least the interrupt processing routine 200 described below
Is made to remain resident on the memory (step 1).
04), the initialization routine ends.

Consider a case where a system call interrupt is generated from the AP or the OS command program after the end of the above-mentioned initialization routine. In this case, since the vector address has been rewritten in step 103 of the initialization routine, the file control program 35
Then, the processing shifts to the interrupt processing routine 200.

FIG. 4 shows this interrupt processing routine 200.
5 is a flowchart for explaining the operation of FIG.

First, it is determined whether the generated system call is a file creation request to the file server 1 (step 201).

As a result of this determination, if the request is not a creation request to the file server 1, the process jumps to the system call interrupt vector address of the OS 34 stored in step 103 (ie, the interrupt processing routine of the redirector 32) (step 203).

On the other hand, as a result of the determination, the file server 1
If the request is a creation request to the network OS1, a file creation request is issued to the network OS1 by designating the attribute stored in step 102 (step 202).

The creation request in step 202 is made via the network driver 33, the network 5, and the network driver 13 as described above. The network OS 14 sets the attribute specified in the creation request in a file and creates data. The OS 14 receives a bit indicating the attribute. The OS 14 creates directory information when creating a file, writes the received attribute therein, and stores it in the storage device 2.

As shown in FIG. 10, directory information includes, for example, a file name 601 and attribute information 6.
02, update time 603, update date 604, FAT entry number 605 (by referring to this entry number, the address where the file is stored can be known), and file size 606.

Such a file control program 35
The file creation via the interrupt processing routine 200 is effective until the interrupt vector address of the system call is returned to the entry address of the interrupt processing routine of the redirector 32. For this reason, only by creating in the same procedure as in the prior art, desired attributes (including extended attributes) can be automatically set for a plurality of files having the same attribute.

Next, FIG. 5 shows the file control program 3
5 is a flowchart showing an embodiment of a method for automatically setting and automatically canceling attributes according to No. 5.

When the program is started, first, a file control program initialization routine is executed (step 1).
00). The contents of this initialization routine are the same as those already described with reference to FIG.

Next, the user inputs the AP and OS command names (step 301). The program specified by the command name in step 301 is
2 is started as a child process and executed in step 303. When a system call interrupt occurs during execution of an AP or OS command (step 303), the system call is processed by a file control program interrupt processing routine (step 200). The contents of the interrupt processing routine are the same as those already described with reference to FIG. Step 3
At the same time as the execution of the AP and OS commands of 03 ends, the child process ends.

Thereafter, a file control program end routine is executed (step 400). FIG. 6 shows the contents of the processing of this end routine (step 400). When the end routine is started, first, the system call interrupt vector address changed in the initialization routine (step 103) is restored to the value before the change (step 40).
1). Next, the file control program is terminated, and the memory occupied including the memory resident part is released (step 402). As a result, the attribute used when creating a file in the file server 1 generated by the execution of the AP or OS command becomes a default value determined by the network OS 14 or the redirector 32. This default value is used for the attribute unless the file control program 35 is started again. As described above, by executing the end routine at the end of the execution of the file control program and returning the attributes to the default values, it is possible to prevent the attributes used in the previous operation from being set.

Another embodiment of a method for automatically setting and canceling attributes will be described with reference to FIG.

FIG. 7 shows automatic setting of attributes, AP
Of the batch file 500 and the contents of the batch file 500.

Here, the batch file is a text file in which a user sequentially inputs commands from an input device such as a keyboard, a program name, and the like. The user runs this batch file,
A request is issued to the OS. Then, the OS 34 sequentially executes the contents written in the batch file.

FIG. 7 shows an example of a batch file in which three program names FI, APP, and FE are written in order. FI is a program equivalent to the file control program initialization routine 100 described above. APP
Is an application program name. FE is a program equivalent to the above-described file control program end routine 400. Such a batch file 500
Is executed, the same effect as in the embodiment shown in FIG. 5 can be obtained.

In the embodiment described above, the redirector 32
A file control program 35 is provided separately from
By providing the function of the file control program 35 to the redirector 32, the file control program 35
Can be eliminated.

The order of each step in each flowchart is not necessarily the same as in the above embodiment.

The present invention can be used when installing a system,
It can also be used when adding database system information.

The present invention can be used in a stand-alone information processing device. That is, in an information processing apparatus including a file storage device that stores a file having at least a program or data accessible from a plurality of users and an attribute indicating an access right of each user to the program or data, An attribute specified from the outside is input, and this attribute is stored. When a request to create the file occurs, the stored attribute is added to create the requested file. In this way, the attributes are input and stored first, and then the attributes stored at the time of file creation are added and created until the process of returning the attributes to the default values is performed. Work efficiency can also be improved.

Further, as an application of the present invention, a plurality of information processing devices are connected by a network line, and the above-mentioned server function and client function are provided in all the devices, and one information processing device is used in another information processing device. , A file creation request to the storage device is generated, and the information processing device having the storage device requested to create the file can create the file.

[0086]

As described above, by using the present invention, the client OS command or A
It is possible to create a file in the file server generated from the program without changing the program such as P with desired attributes including extended attributes. This eliminates the need for setting the extended attributes after file creation, which has been required conventionally, thereby shortening the work time and improving the work efficiency.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a system according to an embodiment of the present invention.

FIG. 2 is a configuration diagram of a conventional system.

FIG. 3 is a flowchart showing an operation of an initialization routine of a file control program in one embodiment of the present invention.

FIG. 4 is a flowchart showing an operation of an interrupt processing routine of a file control program in one embodiment of the present invention.

FIG. 5 is a flowchart of a method for automatically setting and canceling attributes according to an embodiment of the present invention.

FIG. 6 is a flowchart showing an operation of a file control program end routine according to one embodiment of the present invention.

FIG. 7 is a diagram showing the contents of a batch file of a method for automatically setting and canceling attributes according to an embodiment of the present invention.

FIG. 8 is a diagram showing the contents of a file control program.

FIG. 9 is a diagram illustrating a screen requesting input of an attribute, and a diagram illustrating bits for storing the input attribute;

FIG. 10 is a diagram showing codes stored in a storage device and indicating attributes of a file.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... File server, 2 ... Server storage device, 3 ... Client, 4 ... Client storage device, 5 ... Network, 13 ... Server network driver, 14 ... Network OS, 15 ... Server AP, 30 ... Client A
P, 31 ... AP, OS command, 32 ... Redirector,
33 ... Client network driver, 34 ... O
S, 35: File control program, 100: File control program initialization routine, 200: File control program interrupt routine, 400: File control program end routine, 500: Batch file

──────────────────────────────────────────────────続 き Continuing from the front page Examiner Hirotsune Aizaki (56) References JP-A-2-122348 (JP, A) Shinji Ishiyama, “Solution-type LAN in the 90s of Special Contributions” Mitsubishi Electric Technical Report Vol. 65, No. 12 No. (1991) p. 4 C. Milligan, Network 386 User's Guide, Toppan Corporation, November 25, 1991, p. 51-76, p. 222-273 Special Issue: The Era of Network Computing, Nikkei Byte, Japan, Nikkei BP, December 1, 1990, No. 79, p. 234-284 (58) Field surveyed (Int.Cl. ⁷ , DB name) G06F 12/00 G06F 15/16-15/177

Claims (6)

(57) [Claims] 1. A professional program that can be accessed by a plurality of users.
Gram or data and the program or data
Attribute indicating the access right of each user to
A first file description for storing at least a file
Storage device and a file to be stored in the first file storage device.
First file that generates a request to create a file
Creation request means, and the first file creation request means
When a file creation request occurs, the specified attribute is
Add a butte to create the requested file
File server having first file creating means for performing
Create a file for the device via a network line
A client device comprising means for performing, Atoribi of inputting the attributes that have been instructed from the outside
And an attribute input by the input means.
And a file to be stored in the first file storage device.
File creation request generating a request to create
And when the second file creation request occurs, the
Attribute added to the first file
And a starting unit for starting the generating unit. 2. The client device according to claim 1, wherein
Te, generates an interrupt when the second file creation request occurs
Means for executing the first file creation means in the interruption
A client device. 3. The client device according to claim 1, wherein
Te, the means for changing the interrupt vector address of the system call
Furthermore, the activation means uses the changed vector address.
To activate the first file creation means.
Characteristic client device. 4. The client device according to claim 3, wherein
Te, files with the first file creating means the is activated
When the creation of the modified system call is completed,
Means for restoring the interrupt vector address to the address before change
A client device, further comprising: 5. The client device according to claim 1, wherein
Te, a plurality of access from the user can program or
Data and each use for the program or data
Attribute that indicates the access rights of the
A second file storage device for storing files to be
Provided in the second file creation requesting means, the second file
Request to create a file to be stored in the file storage device
If further generated, the second file creation request means generates said first
Create a file to be stored in one file storage device
Request to store in the second file storage device.
Determine if the request is to create a file to be stored
Determining means, and the second file storage device
Determined to be a request to create a file to be stored
If stored, add the stored attribute
And stores the requested file in the second file
And a second file creating means for creating in the storage device . 6. The client device according to claim 5, wherein
Te, the interrupt when the second file creation request means generates
Means for generating, the interrupt and the second flag in the interrupt.
File creation by the file creation means or the first
Starting file creation means.
Client equipment.