-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
so a few users have reporting seeing 'segmentation fault' when logging in.
this seems to be caused by listlogins (the program that prints your current
login sessions), but i've never been able to reproduce it.
if you see this message logging in:
* run /usr/local/bin/listlogins. if it prints the same thing, do this:
$ gdb /usr/local/bin/listlogins
(gdb) run
(message about SIGSEGV appears)
(gdb) bt
save the output from the 'bt' command and send it to me.
thanks,
river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (SunOS)
iEYEARECAAYFAkh/WPYACgkQIXd7fCuc5vIshQCgpffGX57NP2YASy/e/6z/Lq3t
1toAoJPF0n6olTh4k+0iu/05DA3CTYGi
=Oo14
-----END PGP SIGNATURE-----
(I tried to reply to the new PHP thingy mail before, but my mails
bounced. Resubscribed and trying again)
Since the switch to the new FastCGI PHP wrapper, I observe some
problems with my tools:
1. When using the gzip output handler (default on my tools), output
dies after a screen or two with:
"Content Encoding Error
The page you are trying to view cannot be shown because it uses an
invalid or unsupported form of compression."
2. Intermittent, output of longer-running scripts dies (again, in the
middle of the run):
"Internal Server Error (500)
The server encountered an internal error and is unable to complete
your request at this time. If the problem persists, please contact the
owner of the tool you are trying to use and inform them of this error,
quoting the following information:
* Request host: toolserver.org
* Request path: GET /~magnus/flickr2commons.php"
3. Accessing external sites from the toolserver (e.g., copying files
from flickr to reupload them on Commons) dies in >50% of the cases.
So, yes, I do see significant problems with the wrapper as it is now.
Magnus
Hello,
I need to manage my toolserver account, but i dont have Internet at my
house.
I talk a long time with the admin at my work, but SSH is restricted. I only
can
use 80 and 443 accros a proxy.
I dont understand at all about network, but is it possible to help me ?
Reading the web, i understand :
* if the login.toolserver.org use 443 for ssh it can work ;
* it exists something call http-tunnel (i can't connect to this site cause
restriction, so i dont know what it is)
Do you think it exists a simple solution ? or already exists something like
that on toolserver o_O ?
Thanks a lot for your time.
-bayo
hi,
PHP on hemlock has been changed to use switchboard (a FastCGI PHP wrapper)
instead of CGI php. unless any major problems are uncovered, this change will
be permanent.
if you notice anything strange about PHP since the change, please let me know.
- river.