Re: tzset error

2014-12-06 Thread rl76

06.12.2014 8:27, Brian Inglis пишет:

Corinna Vinschen  cygwin.com> writes:

On Dec  5 14:32, rl76  inbox.ru wrote:



I run Cygwin Terminal and the first line I see the error:
tzset: can not find matching POSIX timezone for Windows timezone "Belarus
Standard Time"
Installed all the latest updates.
Windows 7. Windows Time Zone: (UTC+03:00) Minsk.



There is no "Belarus Standard Time".  The only matching timezone in
this list is "Kaliningrad Standard Time" with region "BY".


Belarus Standard Time was dropped in Dec 2011 Win DST update and replaced by
Kaliningrad Standard time “(UTC+03:00) Kaliningrad, Minsk”, reverted in Aug
2014 Russian time zone updates, which restored Belarus +3:00 Minsk and
readded Kaliningrad +2:00 (RTZ 1).
Check your local Windows TZ selector dropdown or the registry.
The changes already appeared in tz 2014f August release.


http://support.microsoft.com/kb/2998527/en-us



--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: tzset error

2014-12-06 Thread rl76

05.12.2014 16:58, Corinna Vinschen пишет:

On Dec  5 14:32, r...@inbox.ru wrote:

Hello!

I run Cygwin Terminal and the first line I see the error:

tzset: can not find matching POSIX timezone for Windows timezone "Belarus
Standard Time"

Installed all the latest updates.
Windows 7. Windows Time Zone: (UTC+03:00) Minsk.


Oh.  Sorry about that.  Cygwin's tzset is using the conversion list
Windows timezone to POSIX timezone from
http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/zone_tzid.html

There is no "Belarus Standard Time".  The only matching timezone in
this list is "Kaliningrad Standard Time" with region "BY".

However, it seems that the XML conversion list from the same site
(http://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml)
is in a much better (==newer) shape.

[...time passes...]

I updated tzset now and added a script to the Cygwin repo which
allows easier updating this info once in a while.

I created new developer snapshots on https://cygwin.com/snapshots/
Please give the new tzset from cygwin-inst-20141205.tar.xz for your
architecture a try.


Thank you, Corinna! The error was fixed. But there are suspicious 
strings in the source code.


In files cygwin-snapshot-20141205-1\winsup\utils\tzmap.h and 
cygwin-snapshot-20141205-1\winsup\utils\tzmap-from-unicode.org

Kaliningrad Standard Time/BY
  { L"Kaliningrad Standard Time", L"BY", L"Europe/Minsk" },

Best regards, rl76.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



Re: Unexpected messages from sshd with 2014-12-05 snapshot

2014-12-06 Thread Corinna Vinschen
On Dec  5 14:52, Ken Brown wrote:
> I have two local accounts.  When I ssh from one to the other (i.e., ssh
> user2@localhost while logged in as user1), I get many messages like the
> following:
> 
>   0 [main] sshd 3420 build_env: remove: ALLUSERSPROFILE=C:\ProgramData
>1411 [main] sshd 3420 build_env: remove: COMPUTERNAME=XXX
>1475 [main] sshd 3420 build_env: remove:
> ComSpec=C:\windows\system32\cmd.exe
>1524 [main] sshd 3420 build_env: remove: OS=Windows_NT
> [...]
> 
> This is with today's snapshot.  I haven't checked earlier snapshots yet, but
> I could do that if it would help.

Never mind.  I left two debug statements in the code
which I used to check the new functionality described here:
https://cygwin.com/ml/cygwin/2014-12/msg00013.html

Sorry about that.  I checked in a patch and created a new snapshot.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgprQpQXXutgc.pgp
Description: PGP signature


Re: tzset error

2014-12-06 Thread Corinna Vinschen
On Dec  6 12:58, rl76 wrote:
> 05.12.2014 16:58, Corinna Vinschen пишет:
> >On Dec  5 14:32, r...@inbox.ru wrote:
> >>Hello!
> >>
> >>I run Cygwin Terminal and the first line I see the error:
> >>
> >>tzset: can not find matching POSIX timezone for Windows timezone "Belarus
> >>Standard Time"
> >>[...]
> >I created new developer snapshots on https://cygwin.com/snapshots/
> >Please give the new tzset from cygwin-inst-20141205.tar.xz for your
> >architecture a try.
> 
> Thank you, Corinna! The error was fixed.

Thanks for testing.

>  But there are suspicious strings in
> the source code.
> 
> In files cygwin-snapshot-20141205-1\winsup\utils\tzmap.h and
> cygwin-snapshot-20141205-1\winsup\utils\tzmap-from-unicode.org
> Kaliningrad Standard Time/BY
>   { L"Kaliningrad Standard Time", L"BY", L"Europe/Minsk" },

Suspicious?  Did you read the surrounding comment explaining why the old
strings are still in the code?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgpFoYPw2_QY5.pgp
Description: PGP signature


Re: Cygwin AD integration home/shell changes

2014-12-06 Thread Corinna Vinschen
On Dec  5 23:11, Andrey Repin wrote:
> I do understand, that the settings MUST provide at least one sensible result.
> Assuming we get sensible defaults, this will not be an issue for majority of
> people.
> However, for those, who wish to alter the setting, it is better, if they get a
> slap this instant, if the setting is not quite right, rather than if they
> discover issue after a long time is passed.
> Issues with core configuration should not be masked by obscure defaults. IMHO.

"Obscure"?  /home/ is the fallback for a long time.
mkpasswd creates it these days.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgp4i6arMUtJm.pgp
Description: PGP signature


Re: zsh newline issues

2014-12-06 Thread cyg
On 12/4/2014 3:01 PM, cyg wrote:
> $uname -a
> CYGWIN_NT-6.1 host 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 Cygwin
> $mintty --version
> mintty 1.2-beta1 (x86_64-pc-cygwin)
> (C) 2013 Andy Koppe
> License GPLv3+: GNU GPL version 3 or later
> There is no warranty, to the extent permitted by law.
> $zsh --version
> zsh 5.0.6 (x86_64-unknown-cygwin)
> 
> experiencing strange issues with newline, which is not constantly being
> printed with carriage return. E.g.
> 
> $cd ~
> $mkdir foo
> $vim
> ^Z
> 
> [1]  + 4936 suspended  vim
> $vim
> ^Z
> [1]  + 4936 continued  vim
> 
> [1]  + 4936 suspended  vim
> $cd foo
> $vim
> ^Z
> [1]  + 4936 continued  vim
>   (pwd : ~)
> 
> [1]  + 4936 suspended  vim
> (pwd now: ~/foo)
> $vim
> :q
> [1]  + 4936 continued  vim
>   (pwd : ~)
>(pwd now: ~/foo)
> 
> This happens every time with jobs and sometimes with other programs,
> like python printing lines. First time I thought it's because of a
> multi-line prompt, but changing it to a single-line one did nothing.
> Next thing I tried was messing with PROMPT_SP and PROMPT_CR, but one
> does not simply mess with nopromptcr and nopromptsp. The list of options
> (kshoptionprint) is as follows:
> 
> noaliases off
> allexport off
> noalwayslastpromptoff
> alwaystoend   on
> noappendhistory   off
> autocdon
> autocontinue  off
> noautolistoff
> noautomenuoff
> autonamedirs  on
> noautoparamkeys   off
> noautoparamslash  off
> autopushd on
> noautoremoveslash off
> autoresumeon
> nobadpattern  off
> nobanghistoff
> nobareglobqualoff
> bashautolist  off
> bashrematch   off
> nobeepoff
> nobgnice  on
> braceccl  on
> bsdecho   off
> nocaseglobon
> nocasematch   off
> cbasesoff
> cdablevarson
> chasedots off
> chaselinksoff
> nocheckjobs   on
> noclobber on
> combiningcharson
> completealiases   off
> completeinwordon
> continueonerror   off
> correct   on
> correctalloff
> cprecedences  off
> cshjunkiehistory  off
> cshjunkieloopsoff
> cshjunkiequotes   off
> cshnullcmdoff
> cshnullglob   off
> nodebugbeforecmd  off
> dvorakoff
> emacs off
> noequals  off
> errexit   off
> errreturn off
> noevallineno  off
> noexecoff
> extendedglob  on
> extendedhistory   on
> noflowcontrol on
> forcefloatoff
> nofunctionargzero off
> nogloboff
> noglobalexportoff
> noglobalrcs   off
> globassignoff
> globcomplete  off
> globdots  off
> globsubst off
> nohashcmdsoff
> nohashdirsoff
> hashexecutablesonly   off
> nohashlistall off
> histallowclobber  off
> nohistbeepoff
> histexpiredupsfirst   on
> histfcntllock off
> histfindnodupson
> histignorealldups on
> histignoredupson
> histignorespace   on
> histlexwords  off
> histnofunctions   off
> histnostore   off
> histreduceblanks  off
> nohistsavebycopy  off
> histsavenodupson
> histsubstpattern  off
> histverifyon
> nohup on
> ignorebraces  off
> ignoreclosebraces off
> ignoreeof off
> incappendhistory  on
> incappendhistorytime  off
> interactive   on
> interactivecomments   off
> ksharrays off
> kshautoload   off
> kshglob   off
> kshoptionprinton
> kshtypesetoff
> kshzerosubscript  off
> nolistambiguous   off
> nolistbeepoff
> listpackedoff
> listrowsfirst off
> nolisttypes   off
> localloopsoff
> localoptions  off
> localpatterns off
> localtrapsoff
> login on
> longlistjobs  on
> magicequalsubst   off
> mailwarning   off
> markdirs  off
> menucomplete  off
> monitor   off
> nomultibyte   off
> nomultifuncdefoff
> nomultios off
> nonomatch off
> nonotify  off
> nullglob  off
> numericglobsort   off
> octalzeroes   off
> overstrikeoff
> pathdirs  on
> pathscriptoff
> pipefail  off
> posixaliases  off
> posixargzero  off
> posixbuiltins off
> posixcd   off
> posixidentifiers  off
> posixjobs off
> posixstrings  off
> posixtrapsoff
> 

Re: RFC: 1.7.33 problem with user's home directory

2014-12-06 Thread Corinna Vinschen
On Dec  6 00:05, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> >> > I'd appreciate if those not shy to install developer snapshots would
> >> > give this stuff a try in the meantime.
> >> 
> >> I think I'm about to make a script to install snapshots, at this rate it 
> >> seems
> >> the right thing to do.
> >> Is there a direct way to query for the latest snapshot?
> 
> > The snapshots always have a date attached to the filename.
> 
> I mean, if there's a way to know, what is the latest available snapshot?
> If I want to write a script, that fetch [and install] one.
> I can parse the /snapshots/ page, of course, but this is the least desirable
> choice. For multiple reasons. I would like to have a single point, that could
> refer to the very latest snapshot. Even if it is something like
> /snapshots/x86/cygwin-inst-latest.tar.xz redirecting to
> actual latest snapshot, that'd be quite enough.

http://cygwin.com/acronyms/#SHTDI
http://cygwin.com/acronyms/#PGA


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


pgpndseXutTa1.pgp
Description: PGP signature


Re: tzset error

2014-12-06 Thread Brian Inglis
  inbox.ru> writes:

> 06.12.2014 8:27, Brian Inglis пишет:

>> Belarus Standard Time was dropped in Dec 2011 Win DST update and replaced by
>> Kaliningrad Standard time “(UTC+03:00) Kaliningrad, Minsk”, reverted in Aug
>> 2014 Russian time zone updates, which restored Belarus +3:00 Minsk and
>> readded Kaliningrad +2:00 (RTZ 1).
>> Check your local Windows TZ selector dropdown or the registry.
>> The changes already appeared in tz 2014f August release.
 
> http://support.microsoft.com/kb/2998527/en-us

So they missed the August update and didn't actually release the updates
until September! 

The Cygwin tz mapping appears to have three upstreams: tz which is updated
an average dozen times a year (monthly, but may be more frequent for late
breaking changes like Fiji), but only updated by Cygwin about annually in
arrears; Windows which is updated a few times a year, if a lot of licenced
users are affected, and the rest of the changes are addressed with manual TZ
workarounds; and CLDR, which appears to be updated annually in arrears. 

The Cygwin tz maintainer needs to track the tz updates and the Windows
updates, provide patches to keep the CLDR updated, if you depend on it, and
release updates to the tz package and the Windows mapping with every Windows
update. 



--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



[ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.34-002

2014-12-06 Thread Corinna Vinschen
Hi Cygwin friends and users,


I finally released another TEST version of the next upcoming Cygwin
release.  The version number is 1.7.34-002.

The big changes compared to 1.7.34-001, apart from bugfixes and a new
API (qsort_r), are the following:

- The new nsswitch.conf settings "db_home", "db_shell", and "db_gecos"
  to define where and how to fetch home directory, login shell, and
  gecos content.

  Most importantly, this is also documented now.  See the preliminary
  documentation URL below.

- When spawning a process under another user account (sshd, cron, etc),
  the user's default Windows environment is now merged into the new
  processes environment.


If you want to help testing this new release (which I seriously hope
for), you can find it in your setup-x86.exe or setup-x86_64.exe as
"test" release.


The major change in this new release will be the new method to read
account (passwd and group) information from the Windows user databases
directly, without the requirement to generate /etc/passwd and /etc/group
files to generate Unix-like uid and gid.

For your convenience I wrote new documentation.  Since this is a TEST
prerelease, the new documentation is not part of the official docs yet.
Rather have a look at

  https://cygwin.com/preliminary-ntsec.html

If you read it (which I seriously hope for) and it's all just
incomprehensible gobbledygook to you, please say so on the mailing list

  cygwin AT cygwin DOT com

so we have a chance to improve the documentation.

Please give this TEST release a try.

If you find problems in the new features or regressions compared to the
current stable release 1.7.33, please report them to the public mailing
list

  cygwin AT cygwin DOT com


Following is a list of changes in this new release:


What's new:
---

- Cygwin can now generate passwd/group entries directly from Windows
  user databases (local SAM or Active Directory), thus allowing to run
  Cygwin without having to create /etc/passwd and /etc/group files.
  Introduce /etc/nsswitch.conf file to configure passwd/group handling.

  For bordercase which require to use /etc/passwd and /etc/group files,
  change mkpasswd/mkgroup to generate passwd/group entries compatible
  with the entries read from SAM/AD.

- Add -b/--remove-all option to setfacl to reduce the ACL to only the
  entries representing POSIX permission bits.

- Provide Cygwin documentation (PDFs and HTML) for offline usage in
  /usr/share/doc/cygwin-${version}.


What changed:
-

- Revamp Solaris ACL implementation to more closely work like POSIX ACLs
  are supposed to work.  Finally implement a CLASS_OBJ emulation.  Update
  getfacl(1)/setfacl(1) accordingly.

- The xdr functions are no longer exported for newly built executables.
  Use libtirpc-devel instead.

- 32 bit only: Change default values for socket buffer size to raise
  performance on 10Gb networks.

- When spawning a process under another user account, merge the user's
  default Windows environment into the new process' environment.


Bug Fixes
-

- Fix the problem that ptys master side always writes single byte packages
  to the slave side, and pty slaves always read VMIN byte packages from
  the master side if VMIN is > 0.
  Fixes: https://cygwin.com/ml/cygwin-developers/2014-11/msg0.html

- Fix a synchronization problem in signal handling when using pthreads.
  Addresses: https://cygwin.com/ml/cygwin/2014-11/msg00472.html

- Fix an "invalid handle" problem when using flock(2) with a parent process
  holding the lock.
  Addresses: https://cygwin.com/ml/cygwin/2014-12/msg00012.html


To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe
To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe

If you're already running a 32 bit version of Cygwin on 64 bit Windows
machines, you can continue to do so.  If you're planning a new install
of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit
Cygwin version, unless you need certain packages not yet available in
the 64 bit release.


Have fun,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



reload ssh configuration without stopping and starting the service?

2014-12-06 Thread Marilo
I know linux has ways to reload configuration files without restarting a 
service.

Is there a way with cygwin's sshd to reload the configuration files without 
stopping and starting it.

I know of net start sshd, net stop sshd, and I have checked cygrunsrv  
http://web.mit.edu/cygwin/cygwin_v1.3.2/usr/doc/Cygwin/cygrunsrv.README   I see 
options for start stop install and remove. 

I don't see any way to reload configuration.

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple