GSP/Panel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added Cyg-Win

Browse source
This commit is contained in:
Frank Harris 2026-06-06 18:46:40 -04:00
parent 82cbc206eb
commit 413c315806
10586 changed files with 3806249 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

674
Agent-Windows/OGP64/usr/share/doc/Cygwin/COPYING Normal file
View file

@ -0,0 +1,674 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.

30
Agent-Windows/OGP64/usr/share/doc/Cygwin/CYGWIN_LICENSE Normal file
View file

@ -0,0 +1,30 @@
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Unless stated otherwise, the sources under the cygwin subdirectory,
as well as the sources under the cygserver subdirectory linked into
the Cygwin DLL, are licensed under the Lesser Gnu Public License,
version 3 or (at your option) any later version (LGPLv3+). See the
COPYING.LIB file for the exact wording of that license.
Unless stated otherwise, the sources under the cygserver subdir not
linked into the Cygwin DLL, as well as the sources under the lsaauth
and the utils subdirectories are licensed under the Gnu Public License,
version 3 or (at your option) any later version (GPLv3+). See the
COPYING file for the exact wording of that license.
Parts of the sources in any subdirectory are licensed using a BSD-like
license. The affected source files contain explicit copyright notices
to that effect.
Linking Exception:
As a special exception, the copyright holders of the Cygwin library
grant you additional permission to link libcygwin.a, crt0.o, and
gcrt0.o with independent modules to produce an executable, and to
convey the resulting executable under terms of your choice, without
any need to comply with the conditions of LGPLv3 section 4. An
independent module is a module which is not itself based on the
Cygwin library.

52
Agent-Windows/OGP64/usr/share/doc/Cygwin/_autorebase.README Normal file
View file

@ -0,0 +1,52 @@
_autorebase
===========
This package provides scripts to keep the Cygwin system properly
rebased. By default this happens incrementally, which means only
dynamic objects that have been installed after the last run of rebase
will be considered and the current rebase map takes account of the
already rebased parts of the installation. The scripts must be run by
the system administrator or from another account that has all the
necessary access rights.
Over time the rebase map can fragment. By triggering a full rebase,
all dynamic objects on the system are treated as newly installed and
the existing rebase map is cleared before doing the rebase. To
perform a full rebase, execute "rebase-trigger fullrebase". Then shut
down Cygwin including any services you have installed and simply run
setup.exe. The rebase will be performed even when the installation
did not get modified in any way. Subsequent runs of setup.exe will
again rebase in incremental mode.
Some programs allow the user to create or install dynamic objects
after installation. Since these are not part of an installed package,
they wouldn't be rebased automatically, as their location isn't known
to the package system. Entire subtrees to be searched for dynamic
objects can be advertised in /var/lib/rebase/dynpath.d/,
/var/lib/rebase/localpath.d/ and /var/lib/rebase/userpath.d/ for
packaged paths, locally provided paths and user paths, respectively.
The format of files in these directories is one absolute path per
line. The list of suffixes that files need to have to be considered
dynamic objects in these locations is hardcoded as
"dll|so|eln|oct|mex". Files that should be rebased, but do not have
one of these suffixes can be advertised in /var/lib/dynfile.d,
/var/lib/localfile.d and /var/lib/userfile.d for packaged files,
locally provided files and user files, respectively. The format of
files in these directories is one absolute file name per line.
Packagers should name their files after the (main) application package
that creates the dynamic objects at the advertised location and must
not package anything in either the local*.d or user*.d directories.
The local system administrator should only place files in local*.d
directories and otherwise keep the naming scheme as used for packages.
The user*.d file names should start with the account name of the user
the advertised locations belong to.
The user running the installation must have full access rights to all
such paths and all such locations must be available (e.g. remote or
encrypted volumes must be mounted and unlocked, respectively).
The incremental rebase is controlled by the script /usr/bin/rebaselst.
Except for debugging purposes this script should not be run directly
by users. Like any other attempt at rebasing it doesn't work
correctly on a live Cygwin system.

3
Agent-Windows/OGP64/usr/share/doc/Cygwin/alternatives.README Normal file
View file

@ -0,0 +1,3 @@
WARNING. The files in this directory are managed by
the 'alternatives' program. Do not modify by hand.
See 'man alternatives' and '/usr/sbin/alternatives --help'

529
Agent-Windows/OGP64/usr/share/doc/Cygwin/cygrunsrv.README Normal file
View file

@ -0,0 +1,529 @@
This file:
What is cygrunsrv?
What does it do?
How do I use it?
Informative options...
Querying a service
Removing a service
Starting a service
Stopping a service
Installing a service
General Notes
Generic Examples (but very informative)
Specific Examples (for common cygwin services)
**********************************************
What is cygrunsrv?
cygrunsrv is an implementation of an NT/W2K service starter, similar
to Microsoft's INSTSRV and SRVANY programs, or the FireDaemon program.
However, cygrunsrv is a cygwin program itself, so it obviously supports
Cygwin applications better.
**********************************************
What does it do?
cygrunsrv can operate in two basic modes. The first is the
'service management' or 'commandline' mode. This allows you
to install and remove a service from the system registry, or
to start and stop a previously installed service. The second
mode is the 'run a service' or 'daemonize' mode. This mode is
reached ONLY via a special entry point called by the Windows
Service Mananger -- you can't put cygrunsrv in that mode from
the command line. In the 'daemonize' mode, cygrunsrv sets up
the environment (according to flags set via the 'commandline'
mode). It adds '/bin' to the front of the PATH so that the
target service can find cygwin1.dll easily. It (optionally)
redirects stdout, stdin, and stderr to log files or to the
NT/W2K Event Log (event log access not yet implemented).
Finally, cygrunsrv starts the target daemon.
**********************************************
How do I use it?
As stated earlier, there are four basic operations that
cygrunsrv can do in its 'service management' or 'commandline'
mode: install a service (-I or --install), remove a service
(-R or --remove), start a service (-S or --start), or stop
a service (-E or --stop). In addition, the informative
options return information about cygrunsrv itself.
Each mode is discussed in turn, below:
**********************************************
Informative Options
cygrunsrv -h
cygrunsrv --help
print comprehensive help/option listing for cygrunsrv
cygrunsrv -v
cygrunsrv --version
print version information about the cygrunsrv executable
**********************************************
Query a service:
cygrunsrv -Q <svc_name>
cygrunsrv --query <svc_name>
reports on the existence and status of the service. Use the
--verbose or -V flag to receive extra information.
<svc_name> can either specify a local service name, or it can be
"server/svc_name" or "server\svc_name" to specify a service on a
remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
**********************************************
List services installed with cygrunsrv:
cygrunsrv -L [server]
cygrunsrv --list [server]
lists all services that have been installed with cygrunsrv,
one per line. You can use this for example to stop all
running cygwin services as follows:
$ cygrunsrv -L | (while read S; do cygrunsrv -E $S; done)
You can combine this with the -V / --verbose option to get
full details of each service instead of just names.
You can optionally specify a server name to list services installed on
a remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
**********************************************
Remove a service:
cygrunsrv -R <svc_name>
cygrunsrv --remove <svc_name>
removes the service from the registry
<svc_name> can either specify a local service name, or it can be
"server/svc_name" or "server\svc_name" to specify a service on a
remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
**********************************************
Start a service:
cygrunsrv -S <svc_name>
cygrunsrv --start <svc_name>
attempts to start a previously installed service
<svc_name> can either specify a local service name, or it can be
"server/svc_name" or "server\svc_name" to specify a service on a
remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
**********************************************
Stop a service:
cygrunsrv -E <svc_name>
cygrunsrv --stop <svc_name>
attempts to stop a previously started service
<svc_name> can either specify a local service name, or it can be
"server/svc_name" or "server\svc_name" to specify a service on a
remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
**********************************************
Install a service:
At minimum, the following options and arguments MUST be specified
(of course, the short options -I and -p can be used instead of the
long options --install and --path):
cygrunsrv --install svc_name --path /cygwin/style/path/to/daemon.exe
Note that the "svc_name" is the name of the key in the registry under
which the information for this service is stored. More importantly,
it is the name that appears in the Service Manager control panel
applet, and is the name that can be used by 'cygrunsrv --start' (or
'net start') to start the service (* see --disp option). Note that
the svc_name does not HAVE to be the same as the executable name,
but by convention they are usually the same.
<svc_name> can either specify a local service name, or it can be
"server/svc_name" or "server\svc_name" to specify a service on a
remote machine. The server name can be given as simple name or as
fully qualified domain name (server.example.com).
There are a number of additional, optional arguments that may be
specified.
-------------------------------
-P, --crs-path <path>
Optional path to the cygrunsrv.exe executable. Specifying this can be
useful in several situations.
On the local machine, the path to cygrunsrv is by default the path to
the very executable you execute for the -I command. For testing
purposes you could wish to use another cygrunsrv executable than the
one which should be used for starting the service.
On a remote server, the path to cygrunsrv is by default the path in
the system registry key for the Cygwin root directory (what you get
when running `mount | grep " / "' on the remote machine), concatentated
with "\bin\cygrunsrv.exe". This is not failsafe. It might be better
to specify the path to cygrunsrv on the remote machine manually here.
The path can be given in POSIX or Win32 notation. For remote services
it's advisable to use the Win32 notation.
-------------------------------
-a, --args <args>
Optional string with command line options which shall be passed
to the target service when it is started. This option may only be
specified one; to call the target service with two arguments, list
both arguments surrounded by quotes. For example,
cygrunsrv -I foo -p /usr/bin/bar -a "-D -e"
calls with two arguments, as in "/usr/bin/bar -D -e". If you need
to specify a single argument which contains spaces, you can
protect it with single (') or double (") quotes:
(a) cygrunsrv -I foo -p /usr/bin/bar -a "\"foo bar\""
(b) cygrunsrv -I foo -p /usr/bin/bar -a "'foo bar'"
(c) cygrunsrv -I foo -p /usr/bin/bar -a '"foo bar"'
each result in
(a) /usr/bin/bar "foo bar"
(b) /usr/bin/bar 'foo bar'
(c) /usr/bin/bar "foo bar"
(symmetry suggests the following, but it doesn't work. Trust me)
cygrunsrv -I foo -p /usr/bin/bar -a '\'foo bar\''
-------------------------------
-e, --env <VAR=value>
Optional environment strings which are added to the environment
when the service is started. You can add up to 255 environment strings
using multiple `--env' options. Note that '/bin:' is always appended
to the path to allow started applications to find cygwin1.dll. You
may also specify PATH=/a/path:/list if you like, but /bin WILL be
appended.
cygrunsrv -I foo -p /usr/bin/bar -e HOME=/e/services -e TMP=/var/tmp
A single level of quoting with either single (') or double (") quotes
is allowed:
cygrunsrv -I foo -p /usr/bin/bar -e BAR="\"/d/My Documents/services\""
results in an environment where BAR has the value
"/d/My Documents/services" *including the quotes* (the \-escaping and
the outer quotes are required to protect the command itself from bash).
If you don't understand this discussion about quoting, don't worry --
you probably don't need it.
-------------------------------
-d, --disp <display name>
Optional string which contains the display name of the service.
The default value is the service name (svc_name).
cygrunsrv -I svc_name -p /usr/bin/svc.exe -d baz
results in a service whose parameters are stored under the registry key
'svc_name', executes the daemon svc.exe, but shows up in the Services
control panel applet with the name 'baz'. You can start/stop the daemon
using 'cygrunsrv -S svc_name' or 'net start svc_name' -- but it will
report 'The baz service is starting' etc.
-------------------------------
-f, --desc <service description>
Optional service description string. The description string is
displayed in the Windows graphical display for starting and stopping
the service.
-------------------------------
-t, --type [auto|manual]
Optional start type of service. Defaults to `auto' (e.g. this service
will be automatically started at system bootup). 'manual' means the
service must be explicitly started using 'cygrunsrv -S svc_name'
-------------------------------
-u, --user <user name>
Optional user name to start service as. Defaults to SYSTEM account
(also known as the 'LocalSystem' account). The user must have the
"Logon as a service" privilege.
The user name can be given as Cygwin user name as stored in /etc/passwd:
$ grep "LocalService" /etc/passwd
ls:*:19:0:U-NT AUTHORITY\LocalService,S-1-5-19:/tmp:/bin/false
$ cygrunsrv -I svc -p cmd -u ls
or it can be given in NT user name notation. The backslash used to
separate doamin name and user name can be replaced with a slash.
Examples:
$ cygrunsrv -I svc -p cmd -u MY_DOMAIN\\user
$ cygrunsrv -I svc -p cmd -u MY_DOMAIN/user
$ cygrunsrv -I svc -p cmd -u "NT AUTHORITY/LocalService"
$ cygrunsrv -I svc -p cmd -u "NT AUTHORITY"\\LocalService
-------------------------------
-w, --passwd <password>
Optional password for user. Only needed if a user is given. If a
user has an empty password, enter `-w ' with no <password>.
cygrunsrv -I svc_name -p /usr/bin/svc.exe -u foo -w ""
If a user is given but the -w option is not used, then cygrunsrv will
ask for a password interactively. Note that the password is stored in
encrypted form in the registry.
Beginning with Windows XP and 2003 Server, there's a new security setting
turned on by default, which disallows starting services for accounts without
passwords. When you start the Security Policy MMC Snap-In, you'll find it
under Securiy Settings/Local Policies/Security Options. The setting is
called "Accounts: Limit local account use of blank password to console
logon only." You can disable it, but it's highly discouraged. There's
usually no good reason to install a service under an account without
password.
-------------------------------
-0, --stdin <file>
Optional input file used for stdin redirection. Default is /dev/null.
-------------------------------
-1, --stdout <file>
Optional output file used for stdout redirection. Default is
/var/log/<svc_name>.log.
-------------------------------
-2, --stderr <file>
Optional output file used for stderr redirection. Default is
/var/log/<svc_name>.log. (Thus, by default, both stdout and
stderr are redirected to /var/log/<svc_name>.log).
Note, it may soon be possible to redirect thru a pipe to the
logger program (which is part of the inetutils package) so that
messages printed by the target service are stored in the NT/W2K
Event Application Log. For example,
THIS IS NOT YET IMPLEMENTED!!!!
cygrunsrv -I svc_name -p /usr/bin/foo.exe \
--stderr "|/usr/bin/logger -p INFO -t svc_name"
-------------------------------
-x, --pidfile <file>
Optional path for .pid file written by application after fork().
Default is that the application must not fork().
With this option, it is possible to run daemons not providing a
(usually Cygwin-specific) option to prevent fork()ing.
-------------------------------
-s, --termsig <signal>
Optional signal to send to service application to stop
the service. <signal> can be a number or a signal name such as
HUP, INT, QUIT, etc. Default is TERM, which is appropriate for
most daemons.
-------------------------------
-z, --shutsig <signal>
Optional signal to send to service application to stop the service
in case of a system shutdown. This is useful if your service
application wants to allow different actions to be taken on a normal
service stop and on system shutdown. Note that the --shutsig option
only has an effect if you use the --preshutdown or --shutdown option
(see there for more information). The default signal on shutdown is the
termination signal set with --termsig, TERM otherwise.
-------------------------------
-y, --dep <svc_name2>
Optional name of service that must be started before this
new service. The --dep option may be given up to 16 times, listing
another dependent service each time. Try to avoid dependency loops:
that is, if svc_A depends on svc_B, but svc_B depends on svc_A...
-------------------------------
-n, --neverexits
Optional flag that causes cygrunsrv to only report a successful
shutdown of the service to windows when cygrunsrv itself was told
to shutdown and the exec'ed process exited with a zero status. Use
this option when the service should only be started or stopped via
the Windows service mechanism (e.g. cygrunsrv -E, net stop, or via
the services GUI).
-------------------------------
-O, --preshutdown
-o, --shutdown
Optional flags that causes cygrunsrv to terminate the service
application during system shutdown. When in effect, cygrunsrv sends the
shutdown signal (see --shutsig) to the application process when
cygrunsrv learns that the system is shutting down. This gives the
application a short time (usually not more than up to 20 secs) to clean
up and exit gracefully. Note that each Cygwin process also sends SIGHUP
to itself (implicitly) during system shutdown.
Starting with Windows Vista/Longhorn, the --preshutdown option allows to
terminate the service before the real shutdown takes place, giving the
service up to 3 minutes for its shutdown actions.
Only one of the --preshutdown/--shutdown options is allowed. If you use
--preshutdown on operating systems prior to Windows Vista/Longhorn, it
will be silently converted to --shutdown at service runtime.
-------------------------------
-i, --interactive
Optional flag that allows cygrunsrv to interact with the desktop.
When in effect, cygrunsrv can open windows and pop up message boxes.
Equivalent to the "Allow service to interact with desktop" box.
Cannot be used unless the service runs as SYSTEM.
NOTE: The interactive option has not the desired effect anymore,
starting with Windows Vista/Longhorn. Interactive services which are
allowed to interact with the local desktop are deprecated by Microsoft.
To get desktop interaction, your service needs to use other means of
interprocess communication between the actual service application and a
desktop application running in the user context of the desktop user.
-------------------------------
-j, --nohide
When running services interactively (see -i, --interactive option above),
usually a console window pops up, which has been opened by the service
control manager. Beginning with version 0.99, cygrunsrv hides that
console window by default. If you need that console window open, use
the -j or --nohide option. In that case, cygrunsrv keeps the console
window untouched.
**********************************************
Information on mounts:
Services by default are run as the local system account, not your regular
user account. This means that if you have user-mode mounts (i.e. you
selected 'Just Me' in setup.exe) the service will not see them and fail to
start. Cygrunsrv will now attempt to detect this an warn you if /usr/bin
is mounted in user mode. See also <http://cygwin.com/faq/faq.html#SEC33>.
**********************************************
General Notes:
There's currently one caveat, though. If the application behaves as
a "normal" unix daemon and exits after forking a child, cygrunsrv
will immediately stop the service (but the actual daemon keeps running
in the background). This means that you cannot then STOP the daemon
using cygrunsrv, but you must explicit kill it via 'kill -9 <daemon_pid>'
If you fail to do this, you will probably see something like this in
the Windows Application Event Log:
Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
`Cygwin Apache' service started.
immediately followed by
Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
`Cygwin Apache' service stopped.
but 'ps -eaf | grep httpd' shows that httpd IS still running.
To avoid this problem, you must start the application so that it
doesn't fork a daemon but stays resident instead. sshd
for example has to be called with the -D option. squid must be
called with the -N option.
For example,
cygrunsrv -I sshd -p /usr/sbin/sshd -a -D
cygrunsrv -I squid -p /usr/bin/squid -a -N
although other options may be necessary.
**********************************************
Generic Examples
To install the Cygwin application /bin/foo as service "foo" running under
LocalSystem account, no special options:
cygrunsrv -I foo -p /bin/foo
To install /bin/foo as a service "bar" which requires command line options:
cygrunsrv -I bar -p /bin/foo -a '--opt1 --opt2 -x'
To install /bin/foo as a service "baz" which requires a command line option
which contains spaces:
cygrunsrv -I baz -p /bin/foo -a "-x 'this has spaces inside'"
or
cygrunsrv -I baz -p /bin/foo -a '-x "this has spaces inside"'
To install /bin/foo as a service "foo bar" which doesn't automatically
startup when the system boots:
cygrunsrv -I "foo bar" -p /bin/foo -t manual
To install /bin/foo as a service "bongo" which requires settings for the
environment variables "ENV_VAR_1" and "ENV_VAR_2" to run correctly:
cygrunsrv -I bongo -p /bin/foo -e "ENV_VAR_1=important_1" \
-e "ENV_VAR_2=also_important"
To install sshd as service under user `joey' account:
cygrunsrv -I "Joey sshd" -p /usr/sbin/sshd -a '-d' -u joey
cygrunsrv asks for `joey's password interactively. If one wants
to give joey's password (say, "privy23") on the command line:
cygrunsrv -I "Joey sshd" -p /usr/sbin/sshd -a '-D' -u joey -w privy23
To start the service `foo':
cygrunsrv -S foo
To stop the service `foo':
cygrunsrv -E foo
To uninstall the service `foo':
cygrunsrv -R foo
**********************************************
Specific Examples
Please add suggestions for this list...
------------
postgresql:
cygrunsrv --install postmaster \
--path /usr/bin/postmaster \
--args "-D /usr/share/postgresql/data -i" \
--dep ipc-daemon --termsig INT --user postgresql --shutdown
------------
sshd:
cygrunsrv --install sshd \
--path /usr/sbin/sshd \
--args -D
------------
xinetd:
cygrunsrv --install xinetd \
--pidfile /var/run/xinetd.pid \
--path /usr/sbin/xinetd \
--args "-pidfile /var/run/xinetd.pid"
Note that at present, ipc-daemon.exe and inetd.exe contain the
appropriate code to run as Windows services WITHOUT the assistance
of cygrunsrv.
**********************************************
Troubleshooting
If the service fails to start, consider whether the service process
depends on other services and reinstall the service using the `--dep'
parameter to ensure that those other services are running first. In
particular, any service application that uses network services (such
as socket connections) depends on the "LanmanWorkstation" service; this
dependency can be declared as `--dep LanmanWorkstation'. On systems
where "LanmanWorkstation" isn't started you can try using a dependency
on the "Tcpip" service. In that case just add `--dep Tcpip' to the
command line when installing the service.
**********************************************
Contact Information
For support, contact the cygwin mailing list cygwin@cygwin.com. cygrunsrv was originally created by Corinna Vinschen.

198
Agent-Windows/OGP64/usr/share/doc/Cygwin/cygserver.README Normal file
View file

@ -0,0 +1,198 @@
What is Cygserver?
Cygserver is a program which is designed to run as a background service.
It provides Cygwin applications with services which require security
arbitration or which need to persist while no other cygwin application
is running.
The implemented services so far are:
- Control slave tty/pty handle dispersal from tty owner to other
processes without compromising the owner processes' security.
- XSI IPC Message Queues.
- XSI IPC Semaphores.
- XSI IPC Shared Memory.
- Allows non-privileged users to store obfuscated passwords in the
registry to be used for setuid(2) to create user tokens with network
credentials. This service is used by `passwd -R'. Using the stored
passwords in setuid(2) does not require running cygserver. The
registry storage is the same as Windows uses to store passwords for
accounts running Windows services.
Cygserver command line options:
Options to Cygserver take the normal UNIX-style `-X' or `--longoption' form.
Nearly all options have a counterpart in the configuration file (see below)
so setting them on the command line isn't really necessary. Command line
options override settings from the Cygserver configuration file.
The one-character options are prepended by a single dash, the long variants
are prepended with two dashes. Arguments to options are marked in angle
brackets below. These are not part of the actual syntax but are used only to
denote the arguments. Note that all arguments are required. Cygserver
has no options with optional arguments.
The options recognized are:
-f, --config-file <file>
Use <file> as configuration file instead of the default configuration
line. The default configuration file is /etc/cygserver.conf, typically.
The --help and --version options will print the default configuration
pathname.
This option has no counterpart in the configuration file, for obvious
reasons.
-c, --cleanup-threads <num>
Number of threads started to perform cleanup tasks. Default is 2.
Configuration file option: kern.srv.cleanup_threads
-r, --request-threads <num>
Number of threads started to serve application requests. Default is 10.
The -c and -r options can be used to play with Cygserver's performance
under heavy load conditions or on slow machines.
Configuration file option: kern.srv.request_threads
-p, --process-cache <num>
Number of processes which can connect concurrently to cygserver.
Default is 62. Each process connected to cygserver is a synchronization
object which has to be maintained. The data structure to maintain these
processes is the so-called "process cache". In theory, an arbitrary
number of processes could connect to cygserver, but due to the need to
synchronize, the higher the number of connected processes, the more
synchronization overhead exists. By using this option, you can set an
upper limit to the synchronization effort. If more than 62 processes
try to connect to cygserver concurrently, two additional synchronization
threads are necessary, and one for each further 62 concurrent
processes. So, useful values for the --process-cache option are 62, 124,
186, 248, 310. 310 is the maximum value.
Configuration file option: kern.srv.process_cache_size
NOTE: The number of child processes of a single parent process is limited
to 256. So in case of taking advantage of a process cache size beyond 256,
keep in mind that not all of these processes can be child processes of one
single parent process.
-d, --debug
Log debug messages to stderr. These will clutter your stderr output with
a lot of information, typically only useful to developers.
-e, --stderr
Force logging to stderr. This is the default if stderr is connected to
a tty. Otherwise, the default is logging to the system log. By using
the -e, -E, -y, -Y options (or the appropriate settings in the
configuration file), you can explicitely set the logging output as you
like, even to both, stderr and syslog.
Configuration file option: kern.log.stderr
-E, --no-stderr
Don't log to stderr. Configuration file option: kern.log.stderr
-y, --syslog
Force logging to the system log. This is the default, if stderr is not
connected to a tty, e. g. redirected to a file.
-Y, --no-syslog
Don't log to syslog. Configuration file option: kern.log.syslog
-l, --log-level <level>
Set the verbosity level of the logging output. Valid values are between
1 and 7. The default level is 6, which is relatively chatty. If you set
it to 1, you will get only messages which are printed under severe conditions,
which will result in stopping Cygserver itself.
Configuration file option: kern.log.level
-m, --no-sharedmem
Don't start XSI IPC Shared Memory support. If you don't need XSI IPC
Shared Memory support, you can switch it off here.
Configuration file option: kern.srv.sharedmem
-q, --no-msgqueues
Don't start XSI IPC Message Queues.
Configuration file option: kern.srv.msgqueues
-s, --no-semaphores
Don't start XSI IPC Semaphores.
Configuration file option: kern.srv.semaphores
-S, --shutdown
Shutdown a running daemon and exit. Other methods are sending a SIGHUP
to the Cygserver PID or, if running as service under NT, calling
`net stop cygserver' or `cygrunsrv -E cygserver'.
-h, --help
Output usage information and exit.
-v, --version
Output version information and exit.
How to start Cygserver:
Before you run Cygserver for the first time, you should run the
/usr/bin/cygserver-config script once. It creates the default
configuration file and, upon request, installs Cygserver as service
when running under NT. The script only performs a default install,
with no further options given to Cygserver when running as service.
Due to the wide configurability by changing the configuration file,
that's typically not necessary.
It's best practice to run Cygserver as a service under LocalSystem
account. This is the way it is installed for you by the
/usr/bin/cygserver-config script.
The Cygserver configuration file:
Cygserver has many options, which allow to customize the server
to your needs. Customization is accomplished by editing the configuration
file, which is by default /etc/cygserver.conf. This file is read only
once on startup of Cygserver. There's no option to re-read the file on
runtime by, say, sending a signal to Cygserver.
The configuration file determines how Cygserver operates. There are
options which set the number of threads running in parallel, options
for setting how and what to log and options to set various maximum
values for the IPC services.
The default configuration file delivered with Cygserver is installed
to /etc/defaults/etc. The /usr/bin/cygserver-config script copies it to
/etc, giving you the option to overwrite an already existing file or to
leave it alone. Therefore, the /etc file is safe to be changed by you,
since it will not be overwritten by a later update installation.
The default configuration file contains many comments which describe
everything needed to understand the settings. A comment at the start of the
file describes the syntax rules for the file. The default options are shown
in the file but are commented out.
It is generally a good idea to uncomment only options which you intend to
change from the default values. Since reading the options file on Cygserver
startup doesn't take much time, it's also considered good practice to keep
all other comments in the file. This keeps you from searching for clues
in other sources.
If you have problems with Cygserver, or you have found a bug, or you
think you have found a bug, or you don't understand configuration file
options, the mailing list <cygwin@cygwin.com> is the right place to ask
questions.
Have fun!

26
Agent-Windows/OGP64/usr/share/doc/Cygwin/editrights.README Normal file
View file

@ -0,0 +1,26 @@
This small utility allows Windows NT user rights and privileges
to be set from the command line.
Build:
To build editrights, run "make".
To install it, run "make install".
Usage:
To list the access rights granted to a user (e.g. FRED)
editrights -u FRED -l
To do this more verbosely
editrights -u FRED -l -v
To give FRED the SeTcbPrivilege ("Act as part of the operating system")
editrights -u FRED -a SeTcbPrivilege
To remove this right from FRED
editrights -u FRED -r SeTcbPrivilege
To test whether FRED has the SeTcbPrivilege
editrights -u FRED -t SeTcbPrivilege && echo 'FRED has SeTcb...'
CTR 23/Sep/2003.

55
Agent-Windows/OGP64/usr/share/doc/Cygwin/hostname.README Normal file
View file

@ -0,0 +1,55 @@
hostname
----------------------------------------------------------------------
Show host name, domain name or network addresses
This package provides the Debian version of the hostname command.
It can be used to display the system's host name, DNS domain name or
network addresses.
Runtime requirements (these or newer):
cygwin-1.7.22-1
coreutils-8.15-3 (older versions include /usr/bin/hostname)
Build requirements (these or newer):
binutils-2.23.51-1
coreutils-8.15-1
cygport-0.13.0-1
gcc4-core-4.7.3-1
make-3.82.90-1
tar-1.26-1
Canonical homepage:
http://packages.debian.org/unstable/hostname
Canonical download:
http://ftp.debian.org/debian/pool/main/h/hostname/
Upstream contact:
Debian Hostname Team <hostname-devel@lists.alioth.debian.org>
License:
GPLv2+
Language:
C
---------------------------------------------
Port notes:
-------- hostname-3.13-1 -- 2013-08-07 --------
hostname 3.13 2013-06-08
-------- hostname-3.12-1 -- 2013-04-10 --------
Compilation fixes (missing set*name, NIS)
hostname 3.12 2012-12-06
For more information about this package, see the upstream documentation in
/usr/share/doc/hostname.
Cygwin port by: Christian Franke <chrfranke@users.sourceforge.net>
Please address all questions to the Cygwin mailing list at <cygwin@cygwin.com>.

91
Agent-Windows/OGP64/usr/share/doc/Cygwin/openssh.README Normal file
View file

@ -0,0 +1,91 @@
This package describes important Cygwin specific stuff concerning OpenSSH.
The binary package is usually built for recent Cygwin versions and might
not run on older versions. Please check http://cygwin.com/ for information
about current Cygwin releases.
==================
Host configuration
==================
If you are installing OpenSSH the first time, you can generate global config
files and server keys, as well as installing sshd as a service, by running
/usr/bin/ssh-host-config
Note that this binary archive doesn't contain default config files in /etc.
That files are only created if ssh-host-config is started.
To support testing and unattended installation ssh-host-config got
some options:
usage: ssh-host-config [OPTION]...
Options:
--debug -d Enable shell's debug output.
--yes -y Answer all questions with "yes" automatically.
--no -n Answer all questions with "no" automatically.
--cygwin -c <options> Use "options" as value for CYGWIN environment var.
--name -N <name> sshd windows service name.
--port -p <n> sshd listens on port n.
--user -u <account> privileged user for service, default 'cyg_server'.
--pwd -w <passwd> Use "pwd" as password for privileged user.
--privileged On Windows XP, require privileged user
instead of LocalSystem for sshd service.
Installing sshd as daemon via ssh-host-config is recommended.
Alternatively you can start sshd via inetd, if you have the inetutils
package installed. Just run ssh-host-config, but answer "no" when asked
to install sshd as service. The ssh-host-config script also adds the
required lines to /etc/inetd.conf and /etc/services.
==================
User configuration
==================
Any user can simplify creating the own private and public keys by running
/usr/bin/ssh-user-config
To support testing and unattended installation ssh-user-config got
some options as well:
usage: ssh-user-config [OPTION]...
Options:
--debug -d Enable shell's debug output.
--yes -y Answer all questions with "yes" automatically.
--no -n Answer all questions with "no" automatically.
--passphrase -p word Use "word" as passphrase automatically.
Please note that OpenSSH does never use the value of $HOME to
search for the users configuration files! It always uses the
value of the pw_dir field in /etc/passwd as the home directory.
If no home directory is set in /etc/passwd, the root directory
is used instead!
================
Building OpenSSH
================
Building from source is easy. Just unpack the source archive, cd to that
directory, and call cygport:
cygport openssh.cygport all
You must have installed the following packages to be able to build OpenSSH
with the aforementioned cygport script:
zlib
crypt
libssl-devel
libedit-devel
libkrb5-devel
Please send requests, error reports etc. to cygwin@cygwin.com.
Have fun,
Corinna Vinschen
Cygwin Developer
Red Hat Inc.

219
Agent-Windows/OGP64/usr/share/doc/Cygwin/rsync.README Normal file
View file

@ -0,0 +1,219 @@
rsync
------------------------------------------
fast, versatile file synchronizing tool
Fast and versatile file-copying tool which can copy locally and
to/from a remote host. It offers many options to control its behavior,
and its remote-update protocol can minimize network traffic to make
transferring updates between machines fast and efficient. It is widely
used for backups and mirroring and as an improved copy command for
everyday use.
Mini-HOWTO for using the program as a service:
*) have a valid /etc/rsyncd.conf:
man rsyncd.conf
*) install service:
cygrunsrv --help
cygrunsrv -I rsyncd -p /usr/bin/rsync -a "--daemon --no-detach"
*) remove service:
cygrunsrv -R rsyncd
Runtime requirements:
bash - rsync-ssl script
libgcc1
libiconv2
liblz4_1
libzstd1
libssl1.1
libxxhash0
Build requirements:
python3*-commonmark (check /usr/bin/python3 which version)
libiconv2-devel
liblz4-devel
libzstd-devel
libllvm-devel
Canonical homepage:
http://rsync.samba.org
https://packages.debian.org/unstable/rsync
Canonical download:
http://rsync.samba.org/ftp/rsync
Version control repository:
git clone git://git.samba.org/rsync.git
./support/git-set-file-times # optional
./prepare-source
Mailing list:
Forum / Wiki:
IRC channel:
Upstream contact:
Maintainer:
Bugs: https://bugzilla.samba.org/enter_bug.cgi?product=rsync
License:
GPL-3+
Language:
C
------------------------------------------
Build instructions:
unpack rsync-*-src.tar.*
if you use setup to install this source package, it will be
unpacked under /usr/src automatically
cd /usr/src
./rsync*.sh all
------------------------------------------
Files included in the binary distribution:
See Cygwin package archive
------------------------------------------
Port Notes:
----- version 3.3.0-1 -----
- New upstream release 2024-04-26 Jari Aalto
----- version 3.2.3+20200903+git9f9240b-4 -----
- Compile with xxhah support (Cygwin now includes the library)
----- version 3.2.3+20200903+git9f9240b-3 -----
- New upstream release 2020-09-07 Jari Aalto
- Debian 3.2.3 patches included in sources, but NOT relevant to Cygwin
+ disable_reconfigure_req.diff - Remove need to run reconfigure target
+ perl_shebang.patch - Removes usage of env on perl shebang as per Debian Policy 10.4
+ skip_devices_test.patch - Skip "devices" test as it fails on kfreebsd and hurd
----- version 3.2.3+20200903+git9f9240b-2 -----
- New upstream release 2020-09-06 Jari Aalto
- Compile with python36-commonmark
----- version 3.2.3+20200903+git9f9240b-1 -----
- New upstream release 2020-09-05 Jari Aalto
----- version 3.1.3+20200429+gitf7746d0-1 -----
- New upstream release 2020-05-05 Jari Aalto
----- version 3.1.2-1 -----
- New upstream release 2016-01-29 Jari Aalto
- Includes security fix CVE-2014-9512
- Debian 3.1.1 patches included
logdir.patch
- fix the location of the logdir
ssh-6-option.patch
- call ssh with -6 option if rsync was called
with -6, ditto with -4
noatime.patch
- add an option --noatime to request the kernel not to update files'
access times while reading them. See
https://bugzilla.samba.org/show_bug.cgi?id=7249#c5
----- version 3.1.1-1 -----
- New upstream release 2015-02-13 Jari Aalto
----- version 3.1.0-1 -----
- New upstream release 2014-06-17 Jari Aalto
----- version 3.0.9-1 -----
- New upstream release.
----- version 3.0.8-1 -----
- New upstream release.
----- version 3.0.7-1 -----
- New upstream release.
----- version 3.0.6-1 -----
- New upstream release.
Experimentally enabled xattr support (with a small patch).
----- version 3.0.4-2 -----
- Cygwin 1.7 release.
----- version 3.0.4-1 -----
- New upstream release.
----- version 3.0.2-0 -----
- This release produced by: David Rothenberger <daveroth@acm.org>
- As in message: http://www.cygwin.com/ml/cygwin/2008-05/msg00136.html
New upstream release. Fixes a security issue with extended attribute
support, which isn't enabled for Cygwin anyway.
----- version 3.0.1-0 -----
New upstream release.
----- version 3.0.0-0 -----
- New upstream release.
----- version 2.6.9-2 -----
- Security fix patch (kudos to David Rothenberger for pointing it to me):
http://www.suse.de/%7Ekrahmer/rsync-2.6.9-fname-obo.diffq
----- version 2.6.9-1 -----
No patch used.
----- version 2.6.3-1 -----
- Kept Sjoerd Mullender's patch for the textmode issue as the only patch.
----- version 2.6.2-3 -----
- Added Sjoerd Mullender's patch for the new textmode issue:
http://www.cygwin.com/ml/cygwin/2004-09/msg01022.html
----- version 2.6.2-2 -----
- Added patch for the August 2004 security advisory:
http://rsync.samba.org/#security_aug04
----- version 2.6.2-1 -----
- No patch used.
----- version 2.6.0-1 -----
- No patch used.
----- version 2.5.7-2 -----
- Moved man pages under the /usr/share tree.
----- version 2.5.7-1 -----
- Identical to 2.5.6-2, almost:
1. security advisory:
http://www.mail-archive.com/rsync@lists.samba.org/msg08782.html
2. moved documentation under the /usr/share tree
----- version 2.5.6-2 -----
- Compiled against cygwin-1.5.0 experimental library,
with support for 64-bit file offsets and more.
----- version 2.5.6-1 -----
- Compiled with gcc version 3.2 from now on
----- version 2.5.5-2 -----
- Compiled with gcc version 3.2 20020818 (prerelease)
- Included Anthony Heading's patch to avoid dead child processes
http://sources.redhat.com/ml/cygwin/2002-09/msg01155.html
----- version 2.5.5-1 -----
- No special patch was needed for this version.
- Daemon mode sometimes produces "read error: Connection reset by peer" at the
very end of transfer.
Licensed under GPL v2 or later
Cygwin port maintained by Jari Aalto
Copyright (C) 2014-2024 Jari Aalto <jari.aalto@cante.net>
Copyright (C) 2002-2020 Lapo Luchini <lapo@lapo.it>

BIN
Agent-Windows/OGP64/usr/share/doc/Cygwin/screen.README Normal file
View file

Binary file not shown.