problem with apache
hi, cygwin-apps i have the apache-1.3.24-5 under cygwin-1.3.12-3 and one big trouble with it. if i try download big static file from my web server (bigger than 32768 bytes), then data in downloaded file after byte 0x8000 replaced by trash. but script output with any size are downloaded normally. whats wrong? how i can fix it? please help! -- raVen, http://raven.elk.ru/, icq#550428
Re: problem with apache
Dmitry Suhodoev wrote: hi, cygwin-apps i have the apache-1.3.24-5 under cygwin-1.3.12-3 and one big trouble with it. if i try download big static file from my web server (bigger than 32768 bytes), then data in downloaded file after byte 0x8000 replaced by trash. but script output with any size are downloaded normally. whats wrong? how i can fix it? please help! I haven't seen this. I do run it on several machines offering big static files. Can you provide a link to that big file to see what is downloaded?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: nasm-0.98.35-1
Hallo Dean, Am Freitag, 6. Dezember 2002 um 05:10 schriebst du: Just to be clear, you are now volunteering to *maintain* this package, correct? Yes, I would be happy to maintain the package. I just wasn't sure whether Gerrit was still active as a maintainer for nasm or not. I just built some versions, but didn't kept it up to date. I'm pleased to see someone picking up the work. *** I vote pro this package *** Gerrit -- =^..^=
Re: nasm-0.98.35-1
I just built some versions, but didn't kept it up to date. I'm pleased to see someone picking up the work. nasm is definitely useful for much projects, PRO also from me. -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
[Package Update] HTML Tidy 021202
I updated HTML Tidy to latest version I found yesterday. As usual many small bug fixes, but difficult to tell as the site is lacking a Changelog. This version in based on the tidylib, which is also installed (only static). This version, like the original distribution, contains no more a man page as it is way too outdated, please use tidy --help. File are, as usual, there: http://www.lapo.it/tmp/tidy-021202-1-src.tar.bz2 http://www.lapo.it/tmp/tidy-021202-1.tar.bz2 http://www.lapo.it/tmp/setup.hint @ tidy sdesc: HTML Tidy is a program to clean up and correct messy HTML pages ldesc: HTML Tidy is a program to clean up and correct messy HTML pages. Tidy is able to fix up a wide range of problems and to bring to your attention things that you need to work on yourself. curr: 021202-1 category: Text Web -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) smime.p7s Description: S/MIME Cryptographic Signature
Building /etc/passwd from setup.exe
Domain users have had recurrent troubles with /etc/passwd.
Here is why, and a proposed remedy.
TODAY
The currently released setup.exe verifies if /etc/passwd exists.
If it doesn't, setup creates the file /etc/postinstall/passwd-grp.bat
which contains
bin\mkpasswd -l etc\passwd
That file gets executed during postinstall, creating a passwd file
with only local users.
There is also a package base-passwd with one file,
/etc/postinstall/passwd-grp.sh
#!/bin/sh
type=-l
# if USERDOMAIN isn't empty and
#USERDOMAIN isn't the hostname then we are in a domain
if [ ! -z $USERDOMAIN ] [ $USERDOMAIN != `hostname` ] ; then
# domain user
type=-d
fi
# Should we append rather than replace?
if [ ! -e /etc/passwd ] ; then
/bin/mkpasswd ${type} /etc/passwd
fi
if [ ! -e /etc/group ] ; then
/bin/mkgroup ${type} /etc/group
fi
**
That file has no effect if it runs after passwd-grp.bat, because
then the passwd file already exists. I have observed that order,
I don't know if it's deterministic.
So that's why domain users are not included, and why they are included
if they delete /etc/passwd and rerun /etc/postinstall/passwd-grp.sh.done
after setup, as has been suggested on the list.
SOON
On 2002-11-26, setup has been modified and doesn't create passwd-grp.bat
anymore. Consequently passwd-grp.sh will have an effect if passwd doesn't
exist initially. However that will create another set of problems:
1) If the cases of $USERDOMAIN and `hostname` differ, local users will
execute mkpasswd -d
2) Domain users will not execute mkgroup -l nor mkpasswd -l, so they will
be missing the local groups (Users, ...) and future logins of local
users will see HOME = / .
3) mkpasswd -d will contact the PDC, which may or may not succeed, and which
has been reported to take hours to complete. That's dangerous in a
postinstall script.
SUGGESTION
It seems desirable to
- have local users and groups always appear in /etc/passwd and /etc/group
- avoid contacting the PDC in postinstall scripts
- insure that the user running setup.exe is always included in /etc/passwd
Thus I suggest adding a switch --current (-c) to mkpasswd and to change
passwd-grp.sh to
***
#!/bin/sh
if [ ! -e /etc/passwd ] ; then
/bin/mkpasswd -l -c /etc/passwd
fi
if [ ! -e /etc/group ] ; then
/bin/mkgroup -l /etc/group
fi
***
The -c switch would produce a line about the current user if he is a
domain user, without contacting the PDC (using only internal info).
That arrangement will guarantee that the user installing Cygwin will always
have a sane passwd file. Domain users may have group unknown, but this has
no negative side effects. This will cover most cases.
Of course, to perfect the environment, domain users should also run
mkgroup -l -d while they are connected to the PDC, and run
mkpasswd -l -d if they need to know about other domain users.
They can do that at their leisure.
Comments? Suggestions? I volunteer to add -c.
Pierre
Re: Building /etc/passwd from setup.exe
Pierre A. Humblet wrote:
# if USERDOMAIN isn't empty and
#USERDOMAIN isn't the hostname then we are in a domain
if [ ! -z $USERDOMAIN ] [ $USERDOMAIN != `hostname` ] ; then
# domain user
type=-d
fi
# Should we append rather than replace?
if [ ! -e /etc/passwd ] ; then
/bin/mkpasswd ${type} /etc/passwd
fi
if [ ! -e /etc/group ] ; then
/bin/mkgroup ${type} /etc/group
fi
**
That file has no effect if it runs after passwd-grp.bat, because
then the passwd file already exists. I have observed that order,
I don't know if it's deterministic.
So that's why domain users are not included, and why they are included
if they delete /etc/passwd and rerun /etc/postinstall/passwd-grp.sh.done
after setup, as has been suggested on the list.
This ``$type'' should only poll for the current user in the domain. I
and my company would be very upset if I polled for 10's of thousands of
users.
Earnie.
