nfs.conf file:
#
# This is a general configuration for the
# NFS daemons and tools
#
[general]
pipefs-directory=/run/rpc_pipefs
#
[nfsrahead]
# nfs=15000
# nfs4=16000
#
[exports]
# rootdir=/export
#
[exportfs]
# debug=0
#
[gssd]
# verbosity=0
# rpc-verbosity=0
# use-memcache=0
# use-machine-creds=
Output from systemctl status nfs-server:
root@mediapc:/etc# systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled;
preset: enabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└
The issue was investigated because it was found that file shares were not
created on a computer with Debian trixie after the same installation and
configuration procedure had been followed as for Debian bookworm. Results are
being compared with this system. The installation of nfs-kernel-server
Package: apache2
Version: 2.4.46-4
Severity: important
X-Debbugs-Cc: patrickjrdunf...@gmail.com
Description: If apache2 is uninstalled and then reinstalled, the reinstallation
will fail if the
user has removed conf files in /etc/apache2 directory. The script does not copy
these files for
reinsta
I did some more testing with the system and discovered it is an issue
with it attempting to display the greeter on a display that is turned off.
Not an issue with the installation system this time around. Thanks for
your time.
On 29/07/18 15:39, Debian Bug Tracking System wrote:
Thank you f
Package: installation-reports
Boot method: - netinst
image on a pen drive non-UEFI
Image version:
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso
Date: 2018-07-29 15:00 NZST
Machine: Homebuilt desktop with
Intel DB75EN mainboard
Processor: Intel Pe
Here is the simulated install result on one of my other computers also
running Debian 9
Why do I need 110 packages updated and 48 new ones for borgbackup?
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and a
I have the view the same, it should be so easy to resolve this problem
in the config file, it must be so simple to implement
In addition to the problems you mention, developers of third party
applications have to publish this fix and respond to queries of why
altering the volume level in their
After doing a lot of testing I discovered extra parameters are needed in
the mount command which are not required in Stretch (I have multiple
computers and virtual machines running Stretch and none of them have
needed these parameters when mounting a Samba share). The host server is
also runnin
Package: mount
Version: 2.30.2-0.1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
A line was added to /etc/fstab to mount a cifs network share using the same
syntax as works in Stretch on oth
10 matches
Mail list logo