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
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.
'fsck -p ||
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
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 a
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
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 every
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 a
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 a
8 matches
Mail list logo