[docs] xmldocs - docelic modified 3 files

docs at icdevgroup.org docs at icdevgroup.org
Fri May 20 19:06:43 EDT 2005


User:      docelic
Date:      2005-05-20 23:06:42 GMT
Added:     refs     ReadPermission Windows WritePermission
Log:
More config directives documented, and closing for the day.

Revision  Changes    Path
1.1                  xmldocs/refs/ReadPermission


rev 1.1, prev_rev 1.0
Index: ReadPermission
===================================================================
__NAME__ purpose
affect file mode (read permissions, specifically) on Interchange-generated files
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'><literal>user</literal></arg>
	<arg choice='plain'><literal>group</literal></arg>
	<arg choice='plain'><literal>world</literal></arg>
</group>
__END__


__NAME__ description
By default, only the user account that &IC; runs under,
can read and read files created by &IC;. The specified option allows
adjustment of file &glos-mode;s (read permissions, specifically).
__END__

__NAME__ example: Producing desired read and write file modes
<programlisting>
ReadPermission      group
WritePermission     group
</programlisting>
__END__

__NAME__ see also
WritePermission
__END__



1.1                  xmldocs/refs/Windows


rev 1.1, prev_rev 1.0
Index: Windows
===================================================================
__NAME__ purpose
(obsolete) indicate that Interchange is running under Microsoft Windows
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'>0</arg>
	<arg choice='plain'>1</arg>
</group>
__END__


__NAME__ description
The option should be enabled to indicate that &IC; is running on Microsoft
Windows family of products.
</para><para>
However, Unix is best. The Windows version, while perhaps more than just a toy,
is not suitable for high-volume catalog serving. This is mostly due to Windows
NT not fitting the UNIX <function>fork()</function> model which works so well
with &IC;.
</para><para>
On Microsoft Windows, you will want to stop and re-start your &IC; server at
least once per day. You can use a system agent to automate it &mdash; you will
want to stop the server to expire the session database anyway. You need to do
this because &IC; requires the Unix-specific fork() call to spawn multi-tasked
servers, and without multi-tasked servers there is a strong possibility of
a memory leak &mdash; especially if you use embedded &PERL; or conditional tags.
__END__


__NAME__ notes
&IC; support for Microsoft Windows support has been abandoned.
This configuration directive has no purpose; if you think you need it,
think twice.
__END__


__NAME__ example: Enabling "Windows"
<programlisting>
Windows 1
</programlisting>
__END__

__NAME__ see also
LockType
__END__



1.1                  xmldocs/refs/WritePermission


rev 1.1, prev_rev 1.0
Index: WritePermission
===================================================================
__NAME__ purpose
affect file mode (write permissions, specifically) on Interchange-generated files
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'><literal>user</literal></arg>
	<arg choice='plain'><literal>group</literal></arg>
	<arg choice='plain'><literal>world</literal></arg>
</group>
__END__


__NAME__ description
By default, only the user account that &IC; runs under,
can read and write files created by &IC;. The specified option allows
adjustment of file &glos-mode;s (write permissions, specifically).
__END__

__NAME__ example: Producing desired read and write file modes
<programlisting>
ReadPermission      group
WritePermission     group
</programlisting>
__END__

__NAME__ see also
ReadPermission
__END__








More information about the docs mailing list