delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-Id: | <200404171450.i3HEolU6007421@tigris.pounder.sol.net> |
To: | cygwin AT cygwin DOT com |
From: | nicebounce AT trodman DOT com (Tom Rodman) |
Subject: | observation: cygrunsrv -env option: max env var size is 256 chars |
Date: | Sat, 17 Apr 2004 09:50:46 -0500 |
Based on a few tests this morning under 1.5.9(0.112/4/2), the cygrunsrv -env option supports env vars with a string length below 257 characters. Larger env vars seem to get into the registry, but not into the service's env. If I'm right it would be nice if "cygrunsrv --help" showed this. I read the help as saying up to 255 separate env vars may be defined. -- thanks, Tom Rodman perl -e 'print unpack("u", "1\:6UP\,\$\!T\<F\]D\;6\%N\+F\-O\;0H\`");' -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |