Jump to content

dkg

Members
  • Content Count

    73
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by dkg

  1. Previously, nfsmount would mount your NFS shares. nfsclient from the new nfs-utils will not. netmount will not mount nfs shares unless _netdev is specified (I think partly to avoid mounting NFS shares twice, in case both nfsmount and netmount were started on boot). It looks to me you aren't allowed to specify a point version for this option, so it's aborting. The issue isn't that the server doesn't support 4.2, which would be cause for a fallback, it's that you have an invalid argument value.
  2. After looking through everything again, there is another step explained in the gentoo NFS wiki page[1]. I reverted the /etc/conf.d/netmount change, and added "_netdev" as a mount option in fstab. That seems to work, as well. [1] https://wiki.gentoo.org/wiki/NFS
  3. Sorry, my initial post had a typo. It was supposed to say "Both nfsclient and netmount are in the default runlevel."
  4. After studying the related gentoo bug, I found a workaround by changing /etc/conf.d/netmount like so: rc_need="netif.eth0 nfsclient" This fixed both my boot/mount and shutdown/unmount problems. I think nfsclient+netmount in default runlevel is supposed to work though (based on statements by the gentoo dev). I'll probably create a bug from the notes I put together. I just wanted to make sure I wasn't doing something stupid first. :)
  5. Also, if the NFS export is mounted on shutdown, netmount hangs with 'Unmounting network filesystems...'. The logs have this: Feb 2 09:58:44 nymph kdm[4582]: :0[4582]: pam_unix(kde:session): session closed for user dave Feb 2 10:01:08 nymph kernel: nfs: server wolfie not responding, still trying Feb 2 10:01:57 nymph kernel: nfs: server wolfie not responding, timed out Feb 2 10:04:57 nymph kernel: nfs: server wolfie not responding, timed out Feb 2 10:05:02 nymph kernel: nfs: server wolfie not responding, timed out Seems like the network is going down before netmount does it's thing?
  6. My NFS4 mount in /etc/fstab is not mounting on boot. I made the switch from nfsmount to nfsclient as recommended when I updated the system. Both nfsmount and netmount are in the default runlevel. If, after booting, I restart netmount, the NFS mount starts up. Was there something else I'm supposed to do?
  7. So, I've added a 'sleep 10s' to /etc/init.d/samba, which works. Still hoping for a better solution.
  8. A few "essentials" I always install early in the build process: app-misc/tmux app-editors/zile app-admin/syslog-ng app-admin/logrotate sys-process/vixie-cron
  9. That's not a bad idea, but my smb.conf file is practically empty. It has the bare minumum to set up one file share (10 lines). There's nothing to rebuild. I suppose I just need to put samba on a delayed start, but I don't know how to do that without pausing the whole boot process.
  10. I'm using dhcpcd so that the (static) IP address is assigned by the dhcp server which also handles DNS. That way, I only have to manage the IPs and names in one place. I forgot to mention that this configuration used to work fine. The problem may have started after an upgrade of the router (running OpenWRT which handles dhcp), but I'm not positive. Anyway, it ought to be fixable on the funtoo server.
  11. I have a problem with samba on a file server that's been happening for a while, but just now having a closer look. When I boot the server, about the only feedback I find is in /var/log/samba/log.smbd: [2015/03/16 13:31:49, 0] smbd/server.c:1072(main) smbd version 3.6.25 started. Copyright Andrew Tridgell and the Samba Team 1992-2011 So, everything seems fine, but the shares are unresponsive. So I check status: # /etc/init.d/samba status * status: crashed And then this shows up in /var/log/messages: Mar 16 13:33:04 wolfie /etc/init.d/samba[3616]: status: crashed But there are
×
×
  • Create New...