Date: Tue, 13 Jan 2015 19:14:39 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Devops question: freebsd-update needs a real tty to run, problem for automation Message-ID: <54B5B4EF.3010109@freebsd.org> In-Reply-To: <CAG=rPVcLWgXR_7JabjbkCWK=SkrQrgcZmAS=Yde0mE3Qpz8Q=A@mail.gmail.com> References: <CAG=rPVcLWgXR_7JabjbkCWK=SkrQrgcZmAS=Yde0mE3Qpz8Q=A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --M6k9rrJ9MOQP7s9qERx7fW4P4Dw57qpwc Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-01-13 18:11, Craig Rodrigues wrote: > Hi, >=20 > Ahmed Kamal, a devops expert, is helping me to script the steps to > upgrade a cluster of FreeBSD machines. For certain machines, > we want to track the official FreeBSD releases and use freebsd-update > to install official updates. >=20 > We found that when the invocation of freebsd-update was scripted > and not run via a real tty, we can into this error: >=20 > "freebsd-update fetch should not be run non-interactively." >=20 > There are various workarounds mentioned on various web pages. > However, should we modify freebsd-update so that it can work better > when not run via a real tty? This would make it more devops/automation= > friendly. >=20 > The closest thing I have found is "freebsd-update cron", which can fetc= h > the updates and run without a real tty. The only problem with > "freebsd-update cron" > is that it sleeps a random amount of time between 1 and 3600 seconds be= fore > fetching the updates. This is OK when run in a cron job, > but not OK when run as part of a devops automation framework. >=20 > Anybody have ideas as to the best way to proceed in fixing this in > freebsd-update? > -- > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 I think this requirement was originally added when Colin hosted the mirrors for FreeBSD update himself, and was worried about everyone scripting it to run via crontab at midnight every night. It is likely a false requirement, and can be safely removed. Dealing with the merges, only really affects version upgrades, and is less of an issue compared to being able to automate security fixes. --=20 Allan Jude --M6k9rrJ9MOQP7s9qERx7fW4P4Dw57qpwc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUtbTzAAoJEJrBFpNRJZKfnyAP/AtUB53FaCb11OZGWAYSqIB8 EKg3ltMU8Cs9D9qsUcz9O6iTqOy+Zmh3Wjj9XBi4OWfuAEeTkSGmjVQzVi9Fu/kS ulV7+wVyfDOp1meqEL8IOYUoAMrTJmWHAHOLt4jbWOP5MRbv90P2bsLV1soKqnXU rWIy+XGfmumCNGwU0sVIndqzHNYxdOnEvlT5FG8eY5MDrTBFje1RSQ6ymJpOnu0O CFshGSp2x7nZgT34U+jNKbXIdqbjOnVRW7CNxXcpMHojZRnyjZRZoZZzPWiAU6Qt 7iKjO0sgUD6uytLF73VS8rHrqmqfRDV3YlZ0Lbri9DCApU8kzoC/S//Ioz349XF1 XpzwPtIHBdGV4cTc3sH55QQ83f/z0Qz7e1k/uq2MwB+TglQyy8dF72mb8+qojMXw t9lpc11yfqre0DM0IBlQcMmlKfLW2RGlPS4VYHx8ffafnmcA0I/JenK63gBTzmj1 NldDzcNrrl4o7UHz7bhDH0AUi6m4BF1oqJgourIwJ5xS11tTLxpSNrpRanWZamqt tDBVfqk472e0B4WCi9JAy+LbINeAgcmXvOznMCKqqdUyfZNsmyFRgiMjuXD/JBDK Y+JkJ8s/CmcImbzCLIrSOEkCvVbonQ/b7z6cbljamEHFjda4SeqK4+BpV2RbxmVo 3b0ErC+0GSrWHPCcODcR =eLx+ -----END PGP SIGNATURE----- --M6k9rrJ9MOQP7s9qERx7fW4P4Dw57qpwc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54B5B4EF.3010109>