Darren J Moffat wrote:
Shawn Walker wrote:
Darren J Moffat wrote:
What do you mean 'restart pkg.depotd'. How did you publish the
package? via http? or via file:// ? If you use file://, then yes,
you have to either restart the pkg.depotd server or send a SIGUSR1 to
the depot server to trigger a 'graceful restart' similar to Apache
where you have changed configuration and need it to reload the
configuration information.
It was a file:// URI since that is what the on-ips bits use. I switched
it to a http:// URI and the restart wasn't needed after that.
In the future, when you are using a client that supports the new v1
catalog and the repository you are connecting to offers a v1 catalog,
you won't have to restart the depot server for the client to see new
package data as the client retrieves the catalog file directly.
refresh is implicitly done *if it is time to do so* (i.e. four hours
(by default) have elapsed since the last successful refresh). This
prevents adding possibly several seconds to each operation that is
performed just to connect to the server and retrieve/check catalog
data. The --no-refresh just completely disables the implicit
behaviour altogether.
This behaviour is fairly similar in nature to other packaging systems
with the exception that none of them have implicit refresh at last
check...
Makes perfect sense for the general use case. People updating the same
package(s) lots of times in a short period of time (ie less than the
default 4hrs) aren't exactly normal use cases.
I completely agree that its still confusing as heck though. Which is
why we've talked about making image-update (as an example) perform an
'immediate' implicit refresh instead of an 'if-it-is-time' because an
operation such as that is long-running anyway.
If you can suggest ways that we can make this clearer (in terms of
client behaviour; we're aware documentation and configuration interface
is still lacking), I'd be happy to hear them.
I should also note that, eventually, repository operations will be able
to provide the default value for clients instead of it being hard-coded
in the client. For example, if you ran an 'on-nightly' repository,
you'll be able to set refresh_seconds=0, and all clients connecting to
your repository (assuming they haven't overridden this) will always
connect and check for new catalog data when an implicit refresh is
triggered.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
