Date: Tue, 22 Jun 2021 11:54:31 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 256772] sysutils/firstboot-freebsd-update - [patch] - use --not-running-from-cron Message-ID: <bug-256772-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256772 Bug ID: 256772 Summary: sysutils/firstboot-freebsd-update - [patch] - use --not-running-from-cron Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: cperciva@FreeBSD.org Reporter: mike@urgle.com Assignee: cperciva@FreeBSD.org Flags: maintainer-feedback?(cperciva@FreeBSD.org) Created attachment 225991 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D225991&action= =3Dedit patch to use --not-running-from-cron Use the --not-running-from-cron flag to freebsd-update. This means that in the case that the case of rc scripts running without a terminal, the script still doe the right thing. rc scripts running without a terminal is a different bug, probably, but it = is probably better to be robust in the face of them. Especially as t4g.nano instances are an example of h/w with that bug running when running 13.0-RELEASE. This will, however, break freebsd-update for FreeBSD 10.1 and earlier; the --not-running-from-cron flag is present in 10.2 and 11.0 and later. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256772-7788>