What I tend to do for those is just make the filesystems for that machine
read-only.

This is inconvenient to set up/use for several reasons, but it helps make
machines indifferent to surprise reboots. It's handy if the site has
unreliable power (eg solar/battery out in the bush somewhere) or even
simply because people don't realize random Soekris boxes in wiring cabinets
might need to be shut down cleanly.

-Anthony

On Sat, 3 Oct 2009 11:14:16 -0300, "Jose Fragoso"
<inet_use...@samerica.com>
wrote:
> Hi,
> 
>> If that was a wisething to do, we would have already done so. In other
>> words, it is not wise. It's foolish.
>>
>>      -Otto
> 
> I totally agree with you. This should not be in the release.
> 
> However, I have a few obsd boxes working at places where I can
> not reach with ease. What I want to avoid is telling a client
> (who does not know anything about unix or Xbsd), by phone, to
> run 'fsck -y', when the system does not boot, as a last resource,
> before I have to go there myself. Sometimes, not even a console
> is available.
> 
> Thanks for your insight.
> 
> Regards,
> 
> Jose

Reply via email to