Date: Thu, 23 Feb 2012 20:10:10 -0600 From: Robarrght <robarrght@gmail.com> To: Dan Busarow <dan@buildingonline.com> Cc: freebsd-questions@freebsd.org Subject: Re: (c)dialog working differently during boot in script called by rc system than after boot? Message-ID: <CAHreZJN_zFR%2B1R3Nc8cwE4Ppw5nSP9a-9Mpo3gs2NoYuzDnp5w@mail.gmail.com> In-Reply-To: <D218D7FF-C83D-4A80-ADDE-55482816A178@buildingonline.com> References: <CAHreZJOzZfVu56qynx1Tyi1YUkMJOmUyXm6ZD-YWAnFpkv3ZeQ@mail.gmail.com> <D218D7FF-C83D-4A80-ADDE-55482816A178@buildingonline.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Dan. That was exactly what I was missing. I added: export TERM=3Dcons25 to the rc.d script and now my script works as it should, when I want it to do so. I appreciate your help, very much! Robarrght On Thu, Feb 23, 2012 at 3:32 PM, Dan Busarow <dan@buildingonline.com> wrote= : > > On Feb 23, 2012, at 11:21 AM, Robarrght wrote: > >> (Background) >> I have a script that uses dialog or cdialog (system, not devel,) to >> prompt for network settings on my FreeBSD 8.2-RELEASE box. =A0When I >> make certain changes with the script, a reboot is required. =A0But, this >> would not be necessary if I ran the script during boot, before >> networking is setup. =A0I've hooked up my script to the rc boot system. >> >> (Issue) >> The trouble is that when the rc.d system runs the script, instead of >> the proper dialog boxes working as expected, all I get is a cleared >> out black screen with a white arrow locked dead center that won't >> move. =A0After boot, the script works normally. =A0I even have the scrip= t >> running in getty on a virtual console, where it works like a champ. > > Looks like your TERM variable is not set when booting. =A0Not a big surpr= ise really. =A0Try setting > > TERM=3Dcons25 > > in your script before it calls dialog > > Dan > > > >> >> So, what is the hangup? =A0Are there dependencies that (c)dialog needs >> which aren't started yet? >> >> (Troubleshooting) >> If I simply run >> dialog --msgbox "Test message" 6 25 >> in the rc.d file, instead of having it call my script, I get the same >> bad behavior. =A0That suggests that it is not my script, but the >> environment ... right? >> I have played with the order of when the test dialog message (my rc.d >> file) is ordered and even when it goes way at the end, after cron >> starts up, (which is getting pretty close to the end,) no improvement. >> >> I've seen this work on an older FreeBSD 6.2-STABLE box. =A0But, when I >> cranked one of those up and tried the same simple dialog test directly >> out of the rc.d script, it yielded a black and white ascii only >> version of the message box. =A0That was an improvement over what I'm >> getting on my current FreeBSD 8.2-RELEASE version. =A0But, I wish I knew >> what the former magic was. >> >> Does anyone out there see what I'm missing? >> >> Thank you, >> Robarrght >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHreZJN_zFR%2B1R3Nc8cwE4Ppw5nSP9a-9Mpo3gs2NoYuzDnp5w>