Just a follow up. The most sensible solution to me is, to append the
option --batch to portupgrade in the cron job. Then in cron job
portupgrade will not bug me any more.
On 11/6/06, Josh Carroll josh.carroll at psualum.com
http://lists.freebsd.org/mailman/listinfo/freebsd-questions wrote:
*
Today I found the CPU is drained up by 5 instances of
script and dialog, because everyday when portupgrade updates
python, it tried to display a menu in text mode and ask for a few
options (such as whether python should support IPv6 etc), which of
course hangs in cron job.
Some ports have a
On 11/6/06, Josh Carroll [EMAIL PROTECTED] wrote:
Today I found the CPU is drained up by 5 instances of
script and dialog, because everyday when portupgrade updates
python, it tried to display a menu in text mode and ask for a few
options (such as whether python should support IPv6 etc),
On Tuesday 07 November 2006 01:26, Josh Carroll wrote:
[snip: portupgrade waiting in config dialogs]
Some ports have a config make target which will save options. For
ports that do not, you can use pkgtools.conf and set MAKE_ARGS for
that port.
I know the answer is probably going to be one
