Krisbee wrote: 
> Triode, 
> 1. Removing a CIFS mount does not remove the associated "credentials
> file" - should it?
> 
Should now be fixed.

> 
> 2. First time you add a NFS additional services are enabled and started.
> If another new NFS is added the same services are enabled and started
> again. Or, if the first NFS mount is removed and then added again same
> extra services are enabled and started again.  Does this matter?
> 
I'm not sure this is a concern - let me know if you find a problem.

> 
> 3. Using a NFS share can result in this timeout message appearing in
> journalctl:
> 
> > 
Code:
--------------------
  >   > 
  > [root@alarm credentials]# journalctl | grep "AUTH_GSS upcall timed out"
  > Jul 13 17:26:40 alarm kernel: RPC: AUTH_GSS upcall timed out.
  > Jul 14 17:30:36 alarm kernel: RPC: AUTH_GSS upcall timed out.
  > 
--------------------
> > 
> 

This looks harder to work around as the suggested target can't be
enabled on its own (so we would need to start it from another service?)

> 
> 4. When selecting mount type nfs, the share should not be mounted as
> nfs4 as it currently is. An NFs mount should default to vers=3.
The web interface is correctly passing the type selected to mount - are
you suggesting the case when no type is specified?  If so the behaviour
will be whatever mount does...


------------------------------------------------------------------------
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=101624

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to