Package: nfs-common
Version: 1:1.3.4-2.1+deb9u1
Severity: important
Dear Maintainer,
FYI: /usr/share/bug/nfs-common/script warns of error.
in my case: 'cat /etc/fstab|grep nfs >&3' returns 1 due to 'grep'
fail (my nfs is all in autofs). should probably '|| true' that.
to avoid user confus
running:
gizmo:/var/log# uname -a
Linux gizmo 3.16.0-6-amd64 #1 SMP Debian 3.16.56-1+deb8u1 (2018-05-08) x86_64
GNU/Linux
so, i think you can close this side of the bug.
Thanks for the feedback/follow-through!
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.
On 12/14/2017 12:51 PM, Salvatore Bonaccorso wrote:
> Hi Stephen,
>
> On Mon, Dec 04, 2017 at 09:24:55PM +0100, Salvatore Bonaccorso wrote:
>> Hi
>>
>> On Thu, Nov 30, 2017 at 03:35:40PM -0700, Stephen Dowdy wrote:
>>> On 11/30/2017 01:39 PM, Salvatore
it in April, 2015.
It's a 10 NIC NFS server for the department, and often throws the error when i
update files that are likely being read/open by client systems.
(it doesn't have a huge resource consumption load ever and i get that failure)
So, i vote yeah ;)
--stephen
--
Stephen Dowd
IMHO.
Now i have to create multiple exports records with different "-{defaults}",
or put '({options})' on every single host export creating a more complex
exports environment prone to errors.
thanks,
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - sdo...@ucar.edu- http://www.ral.ucar.edu/~sdowdy/
g an audience of
people stuck with non-optimal drivers/hardware that were working perfectly
well (enough) prior to these changes.
thanks
--stephen
--
Stephen Dowdy - Systems Administrator - NCAR/RAL
303.497.2869 - sdo...@ucar.edu- http://www.ral.ucar.edu/~sdowdy/
RE:
[ Severity set to 'important' from 'critical' Request was from maximilian
attems ]
I just wanted to point out that i had difficulty determining HOW to address
the severity field in reportbug.
Because i *do* have a workaround to the "problem", it's not critical to *me*
anymore, and wasn't at
Package: initramfs-tools
Version: 0.85i
Severity: critical
Justification: breaks the whole system
--
Summary:
This problem is in essence (AFAICT) the same as #337176, #420754
I think the solution is to fix the hook-functions to not just
catch a few well known optimized locations, but
8 matches
Mail list logo