-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2000-08-08 at 14:54 Marcus Brinkmann wrote:
>This looks good. Debian has an even finer distinction: > > reload > cause the configuration of the service to be reloaded > without > actually stopping and restarting the service, > > force-reload > cause the configuration to be reloaded if the service > supports > this, otherwise restart the service. > >However, we can always indentify your "reload" with Debian's >"force-reload" and ignore this difference. I think this is a very important distinction. In most cases, it is overkill (no pun intended) to simply kill a service, and then restart it, to let it reload its configuration. Current users' sessions might be terminated unexpectedly, for example, or other overhead might be incurred. A good example of this is the Squid proxy cache, where fully stopping and restarting is very expensive (memory caches need to be built up again, etc). Ideally, every daemon/service should have such "reload config" functionality; nowadays, most of them have it anyway. Cheers, - -- Dimitry Andric <[EMAIL PROTECTED]> PGP key: http://www.xs4all.nl/~dim/dim.asc KeyID: 4096/1024-0x2E2096A3 Fingerprint: 7AB4 62D2 CE35 FC6D 4239 4FCD B05E A30A 2E20 96A3 -----BEGIN PGP SIGNATURE----- Version: Encrypted with PGP Plugin for Calypso Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBOY/4rrBeowouIJajEQLLCwCghGmKpUNPBKluDbLy2G/wqjKLe6kAn1+f gZ4SLsBSfNfqdbrmh/s6zCBc =HYtQ -----END PGP SIGNATURE-----
