Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Revision History |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Revision History | |||||||||||||
Line: 10 to 10 | |||||||||||||
| |||||||||||||
Added: | |||||||||||||
> > |
| ||||||||||||
1. Introduction1.1 Purpose | |||||||||||||
Line: 97 to 98 | |||||||||||||
Log Files | |||||||||||||
Changed: | |||||||||||||
< < | capmaster.log Anything and everything from Master Program gets logged here. Format will be date, time and short description of entry. | ||||||||||||
> > | capmaster.log Anything and everything from Master Program gets logged here. Format is "[MM/DD/YYYY HH:MM] -<entry priority>- <message>". The entry priority is a single character indicating the type of entry made; FATAL ERROR, ERROR, WARNING, INFORMATION, UNKNOWN. | ||||||||||||
Changed: | |||||||||||||
< < | capweb.log Anything and everything from Python CGI scripts gets logged here. | ||||||||||||
> > | capweb.log Anything and everything from Python CGI scripts gets logged here. Same format as above. | ||||||||||||
Pipes | |||||||||||||
Changed: | |||||||||||||
< < | capman.fifo Used for communications between CAPManage and Master Program. | ||||||||||||
> > | man2master.fifo, master2man.fifo Used for communications between CAPManage and Master Program. | ||||||||||||
Changed: | |||||||||||||
< < | webmas.fifo Used for communications between web server and Master Program. | ||||||||||||
> > | web2master.fifo, master2web.fifo Used for communications between web server and Master Program. | ||||||||||||
Component Locations | |||||||||||||
Line: 122 to 123 | |||||||||||||
| |||||||||||||
Added: | |||||||||||||
> > |
| ||||||||||||
5.2 Master ProgramDescription | |||||||||||||
Line: 130 to 132 | |||||||||||||
The Master Program will have the location of the configuration file passed to it when it starts. The configuration file will specify the locations and names of other components the program must manage. If the Master Program is unable to read the configuration file or open a log file, then it will terminate. If it does not know where anything is or it cannot report problems, then it should be stopped from operating. Master_Program_Pseudocode.txt | |||||||||||||
Added: | |||||||||||||
> > | Command line: capmaster pid capconf.xml The caller must specify the location of the master program's process ID (PID) file which is used to ensure that only one instance of the process is running. The second argument is the location of the XML configuration file for the system. | ||||||||||||
Messages
MSG_MASTERHERE [out] Sent to web server when Master Program starts. |
Line: 1 to 1 | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Revision History | |||||||||||||
Line: 9 to 9 | |||||||||||||
| |||||||||||||
Added: | |||||||||||||
> > |
| ||||||||||||
1. Introduction1.1 Purpose | |||||||||||||
Line: 125 to 126 | |||||||||||||
Description | |||||||||||||
Changed: | |||||||||||||
< < | Acts as the coordinator of the entire system; whenever a data-changing action needs to be carried out, then it must go through the master program. The program will be one process which runs through a perpetual loop reading various pipes and responding to the data in each. The main loop will maintain a constant connection to the database so that changes can be made quickly, and reflected in the web interface. | ||||||||||||
> > | Acts as the coordinator of the entire system; whenever a data-changing action needs to be carried out, then it must go through the master program. The program will be one process which runs through a perpetual loop reading various pipes and responding to the data in each. The main loop will maintain a constant connection to the database so that changes can be made quickly, and reflected in the web interface. Only one instance of the program will be running at a time. The Master Program will have the location of the configuration file passed to it when it starts. The configuration file will specify the locations and names of other components the program must manage. If the Master Program is unable to read the configuration file or open a log file, then it will terminate. If it does not know where anything is or it cannot report problems, then it should be stopped from operating. Master_Program_Pseudocode.txt | ||||||||||||
Messages | |||||||||||||
Line: 286 to 288 | |||||||||||||
PROG, used to get user's job progress. When sent from client, contains nothing. When sent from server, contains JobsProgress class specified in Client plug-in definition. TODO: When message is of type AUTH, it must be encrypted. | |||||||||||||
Added: | |||||||||||||
> > | 5.11 Piped message formatMessages will be parsed by lines; a line is terminated by a newline character with ASCII code 0xA. Rather than have a message end with a certain character, it is better to specify the length of the message in a pre-determined line so that the contents of the message are not limited. Messages will follow this format: A message header indicating the nature of the message; single word, all caps. and underscores (ex: MSG_QUIT)An unsigned long integer indicating the length of the message body The message body which may contain any sort of data, or no data | ||||||||||||
6. User Interface Design6.1 Common Appearance and Behavior | |||||||||||||
Line: 384 to 393 | |||||||||||||
| |||||||||||||
Added: | |||||||||||||
> > |
|
Line: 1 to 1 |
---|