[DIPC-CVS] CVS: dipcd/dipcd dipc.allow.5,NONE,1.1 dipc.conf.5,NONE,1.1 dipcd.8,NONE,1.1 Makefile.am,
Brought to you by:
nikatjef
Menu
▾
▴
[DIPC-CVS] CVS: dipcd/dipcd dipc.allow.5,NONE,1.1 dipc.conf.5,NONE,1.1 dipcd.8,NONE,1.1 Makefile.am,1.1.1.1,1.2
|
From: James E. W. <nik...@us...> - 2000-10-01 00:32:12
|
Update of /cvsroot/dipc/dipcd/dipcd In directory slayer.i.sourceforge.net:/tmp/cvs-serv30098/dipcd/dipcd Modified Files: Makefile.am Added Files: dipc.allow.5 dipc.conf.5 dipcd.8 Log Message: Added Manual pages for the DIPC Daemon --- NEW FILE --- .\" Process this file with .\" groff -man -Tascii dipc.allow.5 .\" .TH DIPC.ALLOW 5 "August 1999" Linux "Linux User's Manuals" .SH NAME dipc.allow \ - DIPC access control file .SH DESCRIPTION This file, located in the /etc directory, is read by the .B referee (one of .B dipcd's processes) on start-up, and lists the address of computers which are allowed to take part in a .B DIPC cluster. The computers named in the file don't have to actually be active in the cluster, but they can do so, if they ever want to. This file should also contain the address of the .B referee computer itself if it is also to be in the cluster. These addresses can be in the number-dot (e.g 194.165.8.3) or symbolic (e.g. sun.iust.ac.ir) formats. Using symbolic names may lead to some delay in dipcd's start-up, as it tries to resolve these addresses. There should be one address per line. The '#' symbol can be used as the start of a comment. When a .B SIGHUP signal is encountered, the contents of this file will be re-read. This could be used to change the set of trusted computers on the fly. .B Important Note: The /etc/dipc.allow file should be present in the referee computer. Its existence in non-referee computers is needed only when the .B -s (secure) option is used when starting the dipcd program. .SH FILES .P .B /etc/dipc.allow \- access list used by dipcd .P .B /etc/dipc.conf \- configuration file for dipcd .SH SEE ALSO dipc(1), dipcd(8), dipcker(1), dicref(1), dipcshm(1), dipcx(1), dipc.allow(5), rsh(1), ipc(2) .SH BUGS Please send all bug reports to this address: .P .B lin...@wa... --- NEW FILE --- .\" Process this file with .\" groff -man -Tascii dipc.conf.5 .\" .TH DIPC.CONF 5 "August 1999" Linux "Linux User's Manuals" .SH NAME dipc.conf \ - DIPC configuration file .SH DESCRIPTION This file, located in the /etc directory, is read by .B dipcd on startup to get some necessary information. The general format of the entries in this file is .IP .B <var> = <value>. '#' is used as start of comments. .P For more information, please refer to .B DIPC's documentation. Here are the recognized values for <var>: .IP this_machine The IP address of this machine, in w.x.y.z or in symbolic notation. If symbolic, dipcd will try to resolve the address on start-up. .B This entry should be present in the file. Don't use addresses like 127.0.0.1 or 'localhost' for this entry. Using 'dipc_auto_find' as the value for this entry will indicate to dipcd to use the hostname command to find the needed IP address. .IP referee IP address of the .B referee to whom this machine will refer, in w.x.y.z or in symbolic notation. If symbolic, dipcd will try to resolve the address on start-up. .B This entry should be present in the file. You could set this entry to the same valid IP address as 'this_machine'. Don't use 'dipc_auto_find', or addresses like 127.0.0.1, or 'localhost' for this entry. .IP transfer_mode If this is equal to 'segment', then DIPC will use a segment as the unit of shared memory management and transfer. 'Page' forces DIPC to use pages. The page size is determined by dipc_page_size entry in the dipc.conf file. .IP dipc_page_size If transfer_mode is 'Page', then this value is used as the size of the virtual page size managed and transfered over the network by DIPC, Otherwise it is not used. This value can be a multiple of the system's virtual memory page size. .IP inhibit_shm_signal If equal to 'yes', DIPC will not send a signal to readers or writers of a shared memory. 'no' causes the signals to be sent. .IP employer_referee_timeout The amount of time in seconds that the .B employer will wait for a reply from referee. This is the time a referee has to answer to requests. It is used whenever an employer wants to contact the referee. These include, searching for a IPC structure, and removing or deleting an IPC structure. .IP employer_shm_timeout The amount of time in seconds that the employer will wait for a reply from a .B shared memory manager. This is used when the employer wants to handle a shared memory read or write. If the number of processes accessing a shared memory simultaneously is large, then this time should be increased. .IP employer_worker_timeout The amount of time in seconds that the employer will wait for a reply from a .B worker. Its use includes the time allowed for remote procedure calls. So for example a wait for a semaphore (via a semop() function) should return within this time. This is different from the normal IPC case, where for example a semop() could not return for a very long time. In DIPC, as far as the employer is concerned, there is no way to distinguish between a system call that is not returning fast, and some problem in the remote machine or the network. This time out value should be adjusted for different applications. Remember that the above time-out applies only to requests from other machines, not the one on which the IPC structure was created. Processes on this machine can wait indefinitely. .IP shm_ak_timeout When a computer requests the contents of a shared memory, the responsible shared memory manager will directly or indirectly send it the contents, and then waits for an acknowledgment. This value gives the amount of time in seconds that the shared memory manager will wait for it. .IP referee_timeout After the referee sends the information about an IPC structure to a requesting machine, it will wait for this amount of time to receive a reply, to find out if the machine created an structure with the corresponding key or not. .IP shm_hold_timeout This gives the .B time quantum in split seconds, for the shm_man. It is used in scheduling machines who request to access the shared memory, and determines the minimum time that a computer can access the shared memory before it is given to someone else. It is not possible to disable this timeout in any way. .P Positive time-out values indicate that you want the time-out to be used. A zero or negative value means that you don't want dipcd to use the time-out mechanism for that particular action. So you can control individual time-outs. As mentioned before, you can use the -t command line argument to disable the whole time-out mechanism, regardless of individual time-out values. The exception here is the shm_hold_timeout, which is always used. These entries can be omitted, in which case default values will be used. .SH EXAMPLE this_machine = 191.72.3.0 #address of this machine referee = 191.72.3.0 # address of the referee. transfer_mode = Segment dipc_page_size = 8192 inhibit_shm_signal = No employer_referee_timeout = 55 employer_shm_timeout = 56 employer_worker_timeout = 300 shm_ak_timeout = 38 referee_timeout = 18 shm_hold_timeout = 0.6 .SH FILES .P .B /etc/dipc.conf \- configuration file for dipcd .P .B /etc/dipc.allow \- access list used by dipcd .SH SEE ALSO dipc(1), dipcd(8), dipcker(1), dicref(1), dipcshm(1), dipcx(1), dipc.allow(5), rsh(1), ipc(2) .SH BUGS Please send all bug reports to this address: .P .B lin...@wa... --- NEW FILE --- .\" Process this file with .\" groff -man -Tascii dipcd.8 .\" .TH DIPCD 8 "August 1999" Linux "Linux User's Manuals" .SH NAME dipcd \ - Distributed Inter\-Process Communication Daemon .SH SYNOPSIS .B dipcd [-tunsvcd] .SH DESCRIPTION .B dipcd is the user space part of DIPC running with root privileges. It does all the decision making, manages the requests, and transfers data to the requesting machines. It should be running on all the computers in the cluster. .B dipcd uses ordinary means to access IPC structures (e.g. using a msgsnd() to send a message), but is, in some ways, treated differently by the kernel, enabling it to do things that ordinary user processes can not do. .B dipcd creates several processes to do its job. Some of these processes set up a UNIX domain socket (back door), and allow other processes to see and change information which are important for DIPC's operations. DIPC's tools (dipcker, dipcref, dipcshm, and dipcx) use this feature. .SH OPTIONS .IP -t disables the time-out mechanism of dipcd, meaning that dipcd will not use any time-out to detect possible problems. Please refer to DIPC's documentation (the theory file) for more information about time-outs. .IP -u signals dipcd to use UDP/IP. The default is TCP/IP. All the computers in the same cluster should use the same networking protocol. .IP -n causes dipcd to convert the outgoing data to network byte order. This is of use in heterogeneous systems. .IP -s makes DIPC more secure by causing the front_end process not to respond to any request from a computer who's address is not in the /etc/dipc.allow file. .B (NOTE: Every computer that uses this option SHOULD also have the /etc/dipc.allow file. .IP -v makes the dipcd program verbose: dipcd will display messages as it does its work. This is mainly of interest for debugging. It could also be used by graphical simulators to trace the system. Each message starts like this: [<task_no.>@<file_name>:<line_no.>]{<hours>:<minutes>:<seconds>:<100th sec>} (The time is measured relative to the start of dipcd. This is followed by the actual message.) .IP -c tells dipcd to log information related to the data conversion routines. The conversions are needed in heterogeneous environments. .IP -d logs the converted information. Some of these information are also logged by the '-v' argument. .P .B NOTE: dipcd outputs its logs to stderr, so you may want to redirect it to a file. Beware that using -v, -c or -d can lead to the generation of an enormous amount of data in a short time. .SH FILES .P .B /etc/dipc.conf \- configuration file for dipcd .P .B /etc/dipc.allow \- access list used by dipcd .SH SEE ALSO dipc(1), dipcker(1), dicref(1), dipcshm(1), dipcx(1), dipc.allow(5), dipc.conf(5), rsh(1), ipc(2) .SH BUGS Please send all bug reports to this address: .P .B lin...@wa... .SH WEB SITE Further information about DIPC can be found at the web site: .B http://wallybox.cei.net/dipc/ .SH AUTHOR ka...@cs... ka...@wa... Index: Makefile.am =================================================================== RCS file: /cvsroot/dipc/dipcd/dipcd/Makefile.am,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -r1.1.1.1 -r1.2 *** Makefile.am 2000/09/24 03:56:08 1.1.1.1 --- Makefile.am 2000/10/01 00:32:10 1.2 *************** *** 6,10 **** SUBDIRS = docs ! EXTRA_DIST = back_end.c dipc.c dipcd.h employer.c front_end.c funcs.h referee.c shm_man.c support.c worker.c dipc.allow dipc.conf install-data-local: --- 6,10 ---- SUBDIRS = docs ! EXTRA_DIST = back_end.c dipc.c dipcd.h employer.c front_end.c funcs.h referee.c shm_man.c support.c worker.c dipc.allow dipc.conf dipcd.8 dipc.allow.5 dipc.conf.5 install-data-local: *************** *** 13,20 **** --- 13,29 ---- $(mkinstalldirs) /etc/ $(INSTALL_DATA) dipc.conf /etc/dipc.conf + $(mkinstalldirs) /usr/man/man8/ + $(INSTALL_DATA) dipcd.8 /usr/man/man8/dipcd.8 + $(mkinstalldirs) /usr/man/man5/ + $(INSTALL_DATA) dipc.allow.5 /usr/man/man5/dipc.allow.5 + $(mkinstalldirs) /usr/man/man5/ + $(INSTALL_DATA) dipc.conf.5 /usr/man/man5/dipc.conf.5 uninstall-local: -rm -f /etc/dipc.allow -rm -f /etc/dipc.conf + -rm -f /usr/man/man8/dipcd.8 + -rm -f /usr/man/man5/dipc.allow.5 + -rm -f /usr/man/man5/dipc.conf.5 ####### kdevelop will overwrite this part!!! (end)############ |