2008/6/18 Detlef [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > 1. It should be possible to limit the access to a pkg.depotd on a > IP-Adress base. So people can limit who will use their repository. Or > should ipfilter be used here ? Who has an example that could used ? > (Ok having all open is the standard ;-)
It is my belief that ip-based mechanisms should be enforced by existing infrastructure, and not by the depot server itself. Since the most common configuration for a depot server will be reverse proxied behind an Apache server, you can also use Apache's mechanisms for ip-based enforcement in addition to firewalls and the like. > 2. pkg.depotd should have an option to switch off the logging. Otherwise > it will create a lot output into smf log-files or on the console. Ok > this output is very useful for debugging purposes, but not for > "production" when providing packages for a lot of clients. As for the information not being useful in "production" -- I will have to disagree. The data in the access logs for the depot server can provide a rich dataset from which to determine popularity of packages, frequency of updates, and a number of other bits of information. In addition, seeing the errors is quite helpful even in a "production" environment since many of the errors can be caused by configuration or other issues on the server itself. I personally believe that errors, at the very least, should always be logged. I know that the new depot server code is capable of disabling or enabling logging completely, however, I will have to check and see if it supports logging based on the severity of the message. My preference would be to let you specify which severities you want logged, "none", "all", "errors", "warnings", etc. Cheers, -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
