Re: Commands not working as expected.

[Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>]

On 2016-09-11 17:03, Brian S. Wilson wrote:
> I updated my Cygwin instance to day and ran the date command.  For some
> reason it spit out only the UTC time, not the EST time and date
> information I was expecting.  When I ran the "man date" command to see
> if anything had changed in the usage, I got the following error messages.
>
> I tried to update Cygwin again; but got the same results.
>
> $ man date
>       1 [main] man 7788 child_info_fork::abort: C:\cygwin\bin\cygz.dll:
> Loaded to different address: parent(0x1E0000) != child(0xB70000)
> man: fork failed: Resource temporarily unavailable
>
> $ man man
>       1 [main] man 5524 child_info_fork::abort: C:\cygwin\bin\cygz.dll:
> Loaded to different address: parent(0x150000) != child(0xB70000)
> man: fork failed: Resource temporarily unavailable

You can try running setup, without selecting any packages, to clean up anything
left unfinished from the last install, reboot, run setup again with nothing
selected, then run mandb under Cygwin to rebuild man db tables.

When posting, please at least run uname and post output to show
OS and Cygwin platform e.g.:

$ uname -srvmo
CYGWIN_NT-10.0 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin

$ uname -srvmo
CYGWIN_NT-10.0-WOW 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 Cygwin

Check that setup installs completed properly with:

$ ls /bin/*.new
ls: cannot access '/bin/*.new': No such file or directory

Check that all setup postinstall scripts completed properly with:

$ ls /etc/postinstall/[!0z]*.*sh
ls: cannot access '/etc/postinstall/[!0z]*.*sh': No such file or directory

Check the results of your last setup in /var/log/setup.log.full and for
issues in previous recent setups towards the end of /var/log/setup.log.

If you're running Cygwin 32 bit (-WOW...i686), you probably ran out of Cygwin
address space for rebasing dlls - this may be indicated by the problem with
cygz.dll.
If you have rebase problems in 32 bit, you can either deinstall some packages,
or if you run Windows 64 bit, install a Cygwin 64 bit setup and select the same
packages.

Please see adjacent FAQ entries 4.44 https://cygwin.com/faq.html#faq.using.bloda
and 4.45 https://cygwin.com/faq.html#faq.using.fixing-fork-failures

If you still have a problem, please follow the problem reporting guidelines
linked below and attach cygcheck output to your reply.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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