--ftEhullJWpWg/VHq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Ed Wilts <ewilts AT ewilts DOT org> [2005-10-13 15:41]:
> On Thu, Oct 13, 2005 at 02:46:53PM -0400, Wayne T Smith wrote:
> > I hope I'm missing something.  If not, maybe it's time for customers to=
=20
> > demand better delivery of the product (such as a single self-installing=
=20
> > executable that installs and/or updates in one fell swoop)?
>=20
> My preference would to have a running client check for an update on the
> master server before it starts a backup.  If an update is available,
> automatically download it and restart the backup, all without requiring
> a client reboot.  This would mean that the NetBackup admin would only
> need to keep the master server up to date and everything else gets done
> automatically.  None of this manually visiting tens or hundreds of
> clients installing new updates.

There would be some change control issues with something like this. I'm
not sure large scale unmanned software pushes is a good idea in all
cases. If you did have this capability, it should be configurable. The
other needed variation of this is that the software can be pushed over
the existing Netbackup connection instead of relying on rsh or domain
access.

At least Windows clients are closer to being able to push software, but
even that is buggy and requires domain/AD authentication to work
properly.

--=20
David Rock
david AT graniteweb DOT com

--ftEhullJWpWg/VHq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDTyYVMrO4/Yb/xwYRAp/ZAKCPFR8r9ZKbIUHK5d7V1MI6a146+wCeODLU
tlQFS/TJ5AmYG3vgk8pS2nM=
=1bKk
-----END PGP SIGNATURE-----

--ftEhullJWpWg/VHq--