On 2011-12-19, Rudolf Leitgeb wrote:
> Am Montag, 19. Dezember 2011, 13:52:40 schrieb Henning Brauer:
>> gotta compromise for crippled systems. solvable with a little shell
>> script run from cron and rc.shutdown.
>
> Wait: your solution would be to periodically remount some volume
> read/write, m
On 19 December 2011 11:39, Rudolf Leitgeb wrote:
> Am Montag, 19. Dezember 2011, 13:52:40 schrieb Henning Brauer:
>> gotta compromise for crippled systems. solvable with a little shell
>> script run from cron and rc.shutdown.
>
> Wait: your solution would be to periodically remount some volume
> r
* Rudolf Leitgeb [2011-12-19 14:40]:
> Am Montag, 19. Dezember 2011, 13:52:40 schrieb Henning Brauer:
> > gotta compromise for crippled systems. solvable with a little shell
> > script run from cron and rc.shutdown.
> Wait: your solution would be to periodically remount some volume
> read/write, m
On Mon, 19 Dec 2011 14:39:42 +0100
Rudolf Leitgeb wrote:
> Guess what your home router does, and what (if you have one)
> your cell phone does?
It loses unimportant data.
Hennings points stand. One of the beauties of OpenBSD is it's init
which is easy to follow and edit. To give such a feature
Am Montag, 19. Dezember 2011, 13:52:40 schrieb Henning Brauer:
> gotta compromise for crippled systems. solvable with a little shell
> script run from cron and rc.shutdown.
Wait: your solution would be to periodically remount some volume
read/write, merge the changes and then drop back to ro ? You
On Mon, 19 Dec 2011 13:52:40 +0100
Henning Brauer wrote:
> while we're really good in that and fsck almost always succeeds and
> fixes things up i have seen different.
Same here, though I have to admit when there are lots to go through, I
can't rememeber not doing an fsck -y. Usually the datas no
* Rudolf Leitgeb [2011-12-19 10:17]:
> Am Freitag, 16. Dezember 2011, 21:49:18 schrieb Henning Brauer:
> > in these cases - where "runs" is the top priority and manual
> > intervention is hard - you most probably want to run with ro / and an
> > mfs or three.
> This is one nice approach but doesn'
Am Freitag, 16. Dezember 2011, 21:49:18 schrieb Henning Brauer:
> in these cases - where "runs" is the top priority and manual
> intervention is hard - you most probably want to run with ro / and an
> mfs or three.
This is one nice approach but doesn't cover features like user changeable
settings
>> it is possible, like in FreeBSD, to do an automatic "fsck -y" at boot time
>> when
>> the system hangs and need user intervention?
>>
>> In FreeBSD we have the possibility to edit the rc.conf and adding just these
>> lines:
>> ...
>> bac
* Rudolf Leitgeb [2011-12-16 10:50]:
> Am Freitag, 16. Dezember 2011, 10:26:27 schrieb Henning Brauer:
> > there is no solution but a proper remote console access, i. e. cereal.
> > it is completely beyond me why some people accept anything else.
> > yes yes, some/many providers don't offer any. s
* Stefan Beke [2011-12-16 10:57]:
> On Fri, Dec 16, 2011 at 10:26, Henning Brauer wrote:
> > it is completely beyond me why some people accept anything else.
> Because it fits their needs.
util something breaks and trey notice that they're doomed and whine,
yes.
> Sometimes would be preferable
On Fri, 16 Dec 2011 10:49:22 +0100
Rudolf Leitgeb wrote:
> There are setups where the stored data is the most important thing
> and there are setups where the task is the most important thing, and
> for the latter ones an automatic "fsck -y" is the way to go.
Or take advantage of one of OpenBSDs
On Fri, Dec 16, 2011 at 10:26, Henning Brauer wrote:
> it is completely beyond me why some people accept anything else.
Because it fits their needs. Even if there was remote access, it would
hang till someone would notice and use it.
Sometimes would be preferable just to force fix of all inode er
Am Freitag, 16. Dezember 2011, 10:26:27 schrieb Henning Brauer:
> there is no solution but a proper remote console access, i. e. cereal.
> it is completely beyond me why some people accept anything else.
> yes yes, some/many providers don't offer any. so pick one that does.
> you don't buy condoms
there is no solution but a proper remote console access, i. e. cereal.
it is completely beyond me why some people accept anything else.
yes yes, some/many providers don't offer any. so pick one that does.
you don't buy condoms with holes either, no matter how cheap.
* Stefan Beke [2011-12-16 09:5
On Fri, Dec 16, 2011 at 9:49 AM, Stefan Beke wrote:
> I guess I understand what Sebastien is talking about. I used to make
> trips to my cheap serverhosting after power failure too :).Just to
> type Y, yes repair those blocks, while system was hanging at boot.
> Not very pleasant experience...
P
I guess I understand what Sebastien is talking about. I used to make
trips to my cheap serverhosting after power failure too :).Just to
type Y, yes repair those blocks, while system was hanging at boot.
Not very pleasant experience...
On Fri, Dec 16, 2011 at 03:00, Kenneth R Westerback
wrote:
>
On Thu, Dec 15, 2011 at 03:42:19PM +, Kevin Chadwick wrote:
> On Thu, 15 Dec 2011 08:29:40 -0500
> Kenneth R Westerback wrote:
>
> > >
> >
> > You can change the 'fsck -p' in /etc/rc to whatever varient you wish. There
> > is, to my knowledge, no knob.
>
> You probably realise but be aware
On Thu, 15 Dec 2011 08:29:40 -0500
Kenneth R Westerback wrote:
> >
>
> You can change the 'fsck -p' in /etc/rc to whatever varient you wish. There
> is, to my knowledge, no knob.
You probably realise but be aware you can lose data with fsck -y but
only on writable filesystems?
On Thu, Dec 15, 2011 at 09:55:47AM +0100, Sebastien Maerker, Continum wrote:
> Hello,
>
> it is possible, like in FreeBSD, to do an automatic "fsck -y" at boot time
> when
> the system hangs and need user intervention?
>
> In FreeBSD we have the possibility to e
Hello,
it is possible, like in FreeBSD, to do an automatic "fsck -y" at boot time
when
the system hangs and need user intervention?
In FreeBSD we have the possibility to edit the rc.conf and adding just these
lines:
...
background_fsck="NO"
fsck_y_enable="YES"
fs
21 matches
Mail list logo
