Re: Running unattended (ifo FFS thread)

1999-11-07 Thread Jesper Skriver
On Sun, Nov 07, 1999 at 04:57:54PM +0100, Dag-Erling Smorgrav wrote: > Kevin Day <[EMAIL PROTECTED]> writes: > > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, > > even if it's unneeded. This takes ages for me. I believe I submitted a PR > > with a 'fix' to fsck. > > 'fs

Re: Running unattended (ifo FFS thread)

1999-11-07 Thread Dag-Erling Smorgrav
Kevin Day <[EMAIL PROTECTED]> writes: > The problem is that 'fsck -py' ignores the 'p' and will fsck every time, > even if it's unneeded. This takes ages for me. I believe I submitted a PR > with a 'fix' to fsck. 'fsck -p || fsck -y' should do the trick. DES -- Dag-Erling Smorgrav - [EMAIL PROT

Re: Running unattended (ifo FFS thread)

1999-10-29 Thread Anthony Kimball
Quoth [EMAIL PROTECTED]: : : >The problem is that 'fsck -py' ignores the 'p' and will fsck every time, : >even if it's unneeded. This takes ages for me. I believe I submitted a PR : >with a 'fix' to fsck. : : According to the man page, fsck -y and fsck -p are two distincts commands. Here's a pa

Re: Running unattended (ifo FFS thread)

1999-10-28 Thread Philippe Charnier
>The problem is that 'fsck -py' ignores the 'p' and will fsck every time, >even if it's unneeded. This takes ages for me. I believe I submitted a PR >with a 'fix' to fsck. >Kevin According to the man page, fsck -y and fsck -p are two distincts commands. --

RE: Running unattended (ifo FFS thread)

1999-10-27 Thread David Scheidt
On Thu, 28 Oct 1999, Daniel O'Connor wrote: > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating

RE: Running unattended (ifo FFS thread)

1999-10-27 Thread Julian Elischer
On Thu, 28 Oct 1999, Daniel O'Connor wrote: > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locati

Re: Running unattended (ifo FFS thread)

1999-10-27 Thread Daniel O'Connor
On 28-Oct-99 Kevin Day wrote: > > This means that it generally always gets through the fsck.. Of course if > > had to delete files then they're gone, but if you value its ability to stay > > without human intervention its handy. > The problem is that 'fsck -py' ignores the 'p' and will fsck ever

Re: Running unattended (ifo FFS thread)

1999-10-27 Thread Kevin Day
> > > On 27-Oct-99 Remy Nonnenmacher wrote: > > In followup of the FFS thread, I would like to know if there are some > > recommendations for running unattended machines. For exemple, avoiding > > the 'run fsck manually' (for exemple, when co-locating a machine far > > away where it is not p

RE: Running unattended (ifo FFS thread)

1999-10-27 Thread Daniel O'Connor
On 27-Oct-99 Remy Nonnenmacher wrote: > In followup of the FFS thread, I would like to know if there are some > recommendations for running unattended machines. For exemple, avoiding > the 'run fsck manually' (for exemple, when co-locating a machine far > away where it is not possible to get