Mongrel users - Jun 2006 - Mongrel 0.3.13 Pre-Release -- Win32! Win32!

Hello Windows Users!

I have finally got my new computer with it''s win32 build working and
have just done the first pre-release for 0.3.13 that has win32 support.

*** All win32 users should try to grab the pre-release and tell me if it
works. ***

You can install it with:

  $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/
>From EITHER win32 or any other platform (this release is for everyone).

--WORKS FOR EVERYONE.  ALL PEOPLE TEST.--

It''s not only for win32, just the first big one for them.


REPORTING BUGS

Just reply to this so I can fix them fast.  You can also post bugs on
the Mongrel site at:

http://rubyforge.org/tracker/?atid=5145&group_id=1306&func=browse


LATEST BUG FIXES

* Fixes the -B debug mode for Edge Rails (because people really like
raping object_id and class function calls in order to Monkey patch in
their own versions with nasty ass parameters killing all introspection).
* Documentation fixes for pound and mongrel_cluster.
* Fixes group and user changing so that if you are already that user it
will let you.
* Fixes a problem with -C (config file) where many options weren''t
being
set.  Config files now OVERRIDE any command line settings.


OFFICIAL 0.3.13 THIS WEEKEND

Unless a horrible bug is found this pre-release will graduate to an
official release on Sunday.

-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/

> Hello Windows Users!
>
> I have finally got my new computer with it''s win32 build working
and
> have just done the first pre-release for 0.3.13 that has win32 support.
>
> *** All win32 users should try to grab the pre-release and tell me if it
> works. ***
>
> You can install it with:
>
>   $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/
>
Correction!  You have to do these things instead:

gem install win32-service
gem install mongrel --source=http://mongrel.rubyforge.org/releases/
gem install mongrel_service --source=http://mongrel.rubyforge.org/releases/

Then you''ll now not use mongrel_rails_service, but instead just use
mongrel_rails and you''ll get these commands:

 - restart
 - service::install
 - service::remove
 - service::start
 - service::stop
 - start
 - stop
 - version

The service::install, service::remove, service::start, and service::stop
now all do what the mongrel_rails_service sript did.

This means DO NOT DO THIS ON PRODUCTION SITES!!!!!!!!

Sorry for the confusion.  Thanks.

Zed A. Shaw

> Hello Windows Users!
>
> I have finally got my new computer with it''s win32 build working
and
> have just done the first pre-release for 0.3.13 that has win32 support.
>
> *** All win32 users should try to grab the pre-release and tell me if it
> works. ***
>
> You can install it with:
>
>   $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/
>
Correction!  You have to do these things instead:

gem install win32-service
gem install mongrel --source=http://mongrel.rubyforge.org/releases/
gem install mongrel_service --source=http://mongrel.rubyforge.org/releases/

Then you''ll now not use mongrel_rails_service, but instead just use
mongrel_rails and you''ll get these commands:

 - restart
 - service::install
 - service::remove
 - service::start
 - service::stop
 - start
 - stop
 - version

The service::install, service::remove, service::start, and service::stop
now all do what the mongrel_rails_service sript did.

This means DO NOT DO THIS ON PRODUCTION SITES!!!!!!!!

Sorry for the confusion.  Thanks.

Zed A. Shaw

I just played with the service stuff for the first time (win32), and
it seems _almost_ perfect.

The service installed and ran just fine. Stopping the service actually
did stop the service but the call threw an exception. Removing the
service seems to have only disabled the service rather than actually
removing it.


On 6/10/06, zedshaw at zedshaw.com <zedshaw at zedshaw.com>
wrote:
> > Hello Windows Users!
> >
> > I have finally got my new computer with it''s win32 build
working and
> > have just done the first pre-release for 0.3.13 that has win32
support.
> >
> > *** All win32 users should try to grab the pre-release and tell me if
it
> > works. ***
> >
> > You can install it with:
> >
> >   $ gem install mongrel
--source=http://mongrel.rubyforge.org/releases/
> >
>
> Correction!  You have to do these things instead:
>
> gem install win32-service
> gem install mongrel --source=http://mongrel.rubyforge.org/releases/
> gem install mongrel_service --source=http://mongrel.rubyforge.org/releases/
>
> Then you''ll now not use mongrel_rails_service, but instead just
use
> mongrel_rails and you''ll get these commands:
>
>  - restart
>  - service::install
>  - service::remove
>  - service::start
>  - service::stop
>  - start
>  - stop
>  - version
>
> The service::install, service::remove, service::start, and service::stop
> now all do what the mongrel_rails_service sript did.
>
> This means DO NOT DO THIS ON PRODUCTION SITES!!!!!!!!
>
> Sorry for the confusion.  Thanks.
>
> Zed A. Shaw
>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

-- 
Cheers,

Kevin

Actually, forget the removing part -- I needed to close and re-open
the services mmc to see it was actually removed already.

On 6/10/06, Kevin Williams <kevwil at gmail.com>
wrote:
> I just played with the service stuff for the first time (win32), and
> it seems _almost_ perfect.
>
> The service installed and ran just fine. Stopping the service actually
> did stop the service but the call threw an exception. Removing the
> service seems to have only disabled the service rather than actually
> removing it.
>
>
> On 6/10/06, zedshaw at zedshaw.com <zedshaw at zedshaw.com> wrote:
> > > Hello Windows Users!
> > >
> > > I have finally got my new computer with it''s win32 build
working and
> > > have just done the first pre-release for 0.3.13 that has win32
support.
> > >
> > > *** All win32 users should try to grab the pre-release and tell
me if it
> > > works. ***
> > >
> > > You can install it with:
> > >
> > >   $ gem install mongrel
--source=http://mongrel.rubyforge.org/releases/
> > >
> >
> > Correction!  You have to do these things instead:
> >
> > gem install win32-service
> > gem install mongrel --source=http://mongrel.rubyforge.org/releases/
> > gem install mongrel_service
--source=http://mongrel.rubyforge.org/releases/
> >
> > Then you''ll now not use mongrel_rails_service, but instead
just use
> > mongrel_rails and you''ll get these commands:
> >
> >  - restart
> >  - service::install
> >  - service::remove
> >  - service::start
> >  - service::stop
> >  - start
> >  - stop
> >  - version
> >
> > The service::install, service::remove, service::start, and
service::stop
> > now all do what the mongrel_rails_service sript did.
> >
> > This means DO NOT DO THIS ON PRODUCTION SITES!!!!!!!!
> >
> > Sorry for the confusion.  Thanks.
> >
> > Zed A. Shaw
> >
> >
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
> --
> Cheers,
>
> Kevin
>

-- 
Cheers,

Kevin

On 6/10/06, Kevin Williams <kevwil at gmail.com>
wrote:
> I just played with the service stuff for the first time (win32), and
> it seems _almost_ perfect.
>
> The service installed and ran just fine. Stopping the service actually
> did stop the service but the call threw an exception. Removing the
> service seems to have only disabled the service rather than actually
> removing it.
>
Hi Kevin, as Zed said, the problem is how win32-... erh, actually, how
ruby-threading model play with Native Threads.

I''ve been working on workarounds for this, but top of my priority list
are other projects, will work on this 2 weeks from now (starting june
19).

>
> On 6/10/06, zedshaw at zedshaw.com <zedshaw at zedshaw.com> wrote:
> > > Hello Windows Users!
> > >
> > > I have finally got my new computer with it''s win32 build
working and
> > > have just done the first pre-release for 0.3.13 that has win32
support.
> > >
> > > *** All win32 users should try to grab the pre-release and tell
me if it
> > > works. ***
> > >
> > > You can install it with:
> > >
> > >   $ gem install mongrel
--source=http://mongrel.rubyforge.org/releases/
> > >
> >
> > Correction!  You have to do these things instead:
> >
> > gem install win32-service
> > gem install mongrel --source=http://mongrel.rubyforge.org/releases/
> > gem install mongrel_service
--source=http://mongrel.rubyforge.org/releases/
> >
> > Then you''ll now not use mongrel_rails_service, but instead
just use
> > mongrel_rails and you''ll get these commands:
> >
> >  - restart
> >  - service::install
> >  - service::remove
> >  - service::start
> >  - service::stop
> >  - start
> >  - stop
> >  - version
> >
> > The service::install, service::remove, service::start, and
service::stop
> > now all do what the mongrel_rails_service sript did.
> >
> > This means DO NOT DO THIS ON PRODUCTION SITES!!!!!!!!
> >
> > Sorry for the confusion.  Thanks.
> >
> > Zed A. Shaw
> >
> >
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
> --
> Cheers,
>
> Kevin
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On Sat, 2006-06-10 at 09:10 -0600, Kevin Williams wrote:
> I just played with the service stuff for the first time (win32), and
> it seems _almost_ perfect.
> 
> The service installed and ran just fine. Stopping the service actually
> did stop the service but the call threw an exception. Removing the
> service seems to have only disabled the service rather than actually
> removing it.
Yeah, there''s an exception that sometimes gets thrown when you try to
stop the service.  This is due to how the win32-service code is written
so there''s not too much we can do about it right now.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/