I don't think it's necessary to restore the original behavior. When I got confused by this before, the depot didn't actually exit. It stayed running after printing an error message.
If you'd like to catch this problem, print an error message, and have the depot exit(1), that would be awesome, but also not required. -j On Tue, Jun 03, 2008 at 11:17:46PM -0500, Shawn Walker wrote: > 2008/6/3 Shawn Walker <[EMAIL PROTECTED]>: > > One of the changes that occurred with the CherryPy putback is that you > > must specify a port number if you are not running the depot server as > > a privileged user, since it defaults to port 80. > > > > If you don't specify a port number, and you execute the depot as an > > unprivileged user, you'll get a traceback with a permission denied > > error because it will try to connect to port 80 by default. > > > > This change in behaviour was necessary as CherryPy doesn't provide a > > way to trap the port error when it occurs (it happens in a different > > thread than the main one). > > I wrote a simple routine to check port permissions tonight as an > experiment to see how hard it would be to restore the original > behaviour. > > If the new port behaviour is bothersome, I'm more than happy to file a > bug and do a putback since my experiment worked. > > Cheers, > -- > Shawn Walker > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
