Hi Mike,
I'm running the BAT3 board on a TS-7300, running mainly in the
fastboot envornment, with the bat3 daemon started from the
'startfpga' script.
My application reads the bat3 information and when it's been on
battery for the preset length of time (shoter than the value set in
bat3) it kills the bat3 daemon and issues a 'ups-monitor poweroff'
after saving data, closing files and unmounting - just as you have
been doing.
Using the fastboot the bat3 daemon's PID is hidden when in full boot
mode, therefore my code can't kill the daemon and just terminates
after saving it's data and unmounting and waits for the system by the
normal BAT3 shutdown.
If I need to reboot from the full boot environment I simply 'shutdown
-r now'.
I hope this was of help.
PJE
--- In "machv0" <> wrote:
>
> Hi All,
>
> Just got a TS-BAT3 and I'm trying figure out the correct
> shutdown/restart process on power failure. For my application if I
> lose power there really is no proceeding so I'm looking at the BAT3
as
> a means of doing a clean shutdown on my TS7XXX maybe with some user
> notification.
>
> The problem I'm running into is a bit of a chicken & egg scenario
that
> I may just be confused about. I'm starting up the bat3 daemon with
the
> shutdown parameter and when power is lost, shutdown is initiated as
> intended. However, now that the BAT3 has kicked into battery backup
> mode I am unable to reboot the TS7XXX without disconnecting power
via
> JP3 on the BAT3. Maybe people are implementing a hardware solution
for
> this via JP3 on the BAT3? Hadn't thought about that until just now.
>
> Otherwise, Technologic supplies the ups-monitor program that toggles
> JP3 via software. Ok fine. Here is where I'm running into the
chicken
> and egg problem. I can't call ups-monitor until after the bat3
> charging daemon has terminated. If I call ups-monitor from the halt
> script prior to halt it is too soon. It seems that "shutdown -h now"
> sends processes the TERM signal whereas "halt" sends the KILL
signal.
> The bat3 daemon does not terminate with the TERM signal therefore
the
> AVR repsonds with busy when ups-monitor is invoked. If I call it
after
> halt it is too late as the system will be halted. To get around
this I
> can grab the process id for the bat3 daemon and kill it purposefully
> prior to halt, followed by a umount of the compact flash or SD and
any
> other processing I might need to do, followed by a call to
> ups-monitor, which results in power down and therefore "halt" never
> being called.
>
> This is pretty good in that I have the root file system mounted read
> only so even though halt is never invoked maybe it's good enough. I
> guess I'm just wondering if others have run into this, and if so how
> you are handling it. Also I may just be confused so feel free to
tell
> me so.
>
> Mike Van Orden
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|