AW: [Openinteract-dev] working on packages in place

[Kutter Martin]

Hi Perrin,

Actually, I keep my packages in a CVS repository and edit them on my client
machine. I've just writeen a quick-hack script shell script which exports
them as OI2 package, copies 'em via scp to the server, calls oi2_manage
install_package and restarts the httpd.

I would strongly discourage in-place editing - you lose the consistent state
a oi2 package normally provides.

Regards,

Martin Kutter

-----Ursprüngliche Nachricht-----
Auftrag von Perrin Harkins
Gesendet: Freitag, 24. Juni 2005 10:34
Betreff: [Openinteract-dev] working on packages in place
Apologies for the newbie question but... How do the rest of
you work on
OI2 packages? Do you keep exporting and installing them
every time you
make a change, or do you edit them in place after the initial install?
I'm assuming the latter, but the docs seem to suggest one
should install
it again every time.
- Perrin
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
openinteract-dev mailing list
https://lists.sourceforge.net/lists/listinfo/openinteract-dev

[Perrin Harkins]

Post by Kutter Martin
Actually, I keep my packages in a CVS repository and edit them on my client
machine. I've just writeen a quick-hack script shell script which exports
them as OI2 package, copies 'em via scp to the server, calls oi2_manage
install_package and restarts the httpd.
I would strongly discourage in-place editing - you lose the consistent state
a oi2 package normally provides.

But you edit them in place on your client machine? I don't mind extra
steps for going to production, and restarting mod_perl is fine too, but
I don't want to have to do the oi2_manage mambo every time I edit a
file.

By the way, do others have problems with oi2_daemon not letting go of
sockets immediately after you kill it, so you can't restart it right
away?

- Perrin

[Antti M Vähäkotamäki]

Post by Perrin Harkins
By the way, do others have problems with oi2_daemon not letting go of
sockets immediately after you kill it, so you can't restart it right
away?

I think you can fix this by adding:

ReuseAddr = 1

in the [socket] section of your oi2_daemon.ini. I think it would be
pretty safe to set this as default or at least commented out in the
configuration file.

- Antti

[Chris Winters]

Post by Perrin Harkins
...
By the way, do others have problems with oi2_daemon not letting go of
sockets immediately after you kill it, so you can't restart it right
away?

I haven't heard about this before, but I'll put the 'ReuseAddr = 1'
entry into CVS if that seems to work for people.

Chris

--
Chris Winters (***@cwinters.com)
Building enterprise-capable snack solutions since 1988.