Systemd nfs client mount share ???

Just installed systemd, systemd-arch-units and initscripts-systemd as per the wiki and all went well except mounting a nfs share from my server. (networking is OK!)
This is the old working mount command run from rc.local before installing systemd;
mount -t nfs4 -o rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 192.168.0.250:/ /media/SERVER_NYTT &
Did not mount at all with systemd, not even when run manually from command line. From systemd log netfs and nfs-common failed to start.
So I tried from fstab instead;
192.168.0.250:/ /media/SERVER_NYTT nfs rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 0 0
This did work but 'mount' showed that systemd had mounted with nfs default options instead of mine (wsize, rsize ...). Still errors from systemd starting netfs and nfs.
So I disabled netfs and nfs-common/rpcbind from rc.conf and created this systemd file (/etc/systemd/system/192.168.0.250.mount);
[Unit]
Description=ServerNfs
Wants=network.target rpc-statd.service
After=network.target rpc-statd.service
[Mount]
What=192.168.0.250:/
Where=/media/SERVET_NYTT
Type=nfs
Options=rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp
DirectoryMode=0777
StandardOutput=syslog
StandardError=syslog
From the sparce wiki and 'man systemd.mount'. Now nothing happens. With my limited understanding I thought it would start neccessary services (wants) and replace the entry in fstab.
I will now enable systemd services rpcbind, rpcstatd and see what happens.
Overall the transition to systemd went very well indeed; slim, openbox, network, .xinitrc, e4rat all started OK much to my surprise! There's still some fine-tuning to do like nfs, and possibly automounting and at last weeding out unneccessary services.
But any help with this nfs client problem is much appreciated.

swanson wrote:
Do you use any of this;
Alternatively, you can mark these entries in /etc/fstab with the x-systemd.automount and x-systemd-device-timeout= options (see systemd.mount ..
I did read the man for systemd.mount but couldn't make out what to put in the fstab line.
By the way, I renamed the mountfile to the target mountpoint but no success. I then reactivated the fstab line, with the new mountpoint in /mnt and that worked fine with mount -a. Except the mount options are not as I want, as they are in fstab. They were before systemd, and now they are as default for nfs4.
have a look here regarding the x-systemd-automount option. I seem to be only one who has noticed a problem with this option, comment=systemd.automount works fine for automounting though. I haven't changed the wiki because I'm still not sure if the problem is on my side.

Similar Messages

NFS latency when Solaris 10 client mounts Linux NFS server(EMC NAS)

Hello,
One of our developers discovered a problem that for simplicity we call "latency". We have several 5.10 clients that we see the exact same symptoms on when NFS mounting our Celerra. The NAS is running a Linux variant "2.4.9-34.5406.EMC", but before you all jump on the "it's EMC's problem" bandwagon, let me explain. We set up an automated process (Perl) that watches an exported folder for the appearance of a request file (rand.req). When the request file comes in we rename the request file to (rand.sav) and then return a "report" named (rand.res). Very elegent I thought, and it runs at near lightspeed when only Linux NFS clients mount the share and create, monitor, delete, etc any files. In fact there is zero recorded latency from the time the report file appears and when the client detects it. But for all our Solaris 10 clients, they create the request file just fine, and the Perl process running on the Linux box sees the file instantaneously and returns the report, but it takes the Solaris client anywhere from 5 to up to 50 seconds before it see's any change in status for any files the Linux box manipulates. I've tried every possible combination of mount -o options there are including noac, rsize and wsize variants, vers=2, proto=udp, actimeo=0, etc, etc, etc. Nothing seems to be the magic bullet. nfsstat -c shows nothing out of the ordinary. There are no retransmits or dropepd packets anywhere in between, no firewall loads, no connectivity delays whatsoever. I'm completely out of ideas. Any ideas or clues would be greatly appreciated!
thanks
Dave

No specific recommendations. But maybe you can watch the cable and get more information.
Set up a case where the file has been created, then have the client check and snoop the cable at the same time. Does the client actually issue a directory check (or is it just displaying cached information)? Does the response contain the new file?
Something to test anyway...
Darren

New files and folders on a Linux client mounting a Windows 2012 Server for NFS share do not inherit Owner and Group when SetGID bit set

Problem statement
When I mount a Windows NFS service file share using UUUA and set the Owner and Group, and set the SetGID bit on the parent folder in a hierarchy. New Files and folders inside and underneath the parent folder do not inherit the Owner and Group permissions
of the parent.
I am given to understand from this Microsoft KnowledgeBase article (http://support.microsoft.com/kb/951716/en-gb) the problem is due to the Windows implmentation of NFS Services not supporting the Solaris SystemV or BSD grpid "Semantics"
However the article says the same functionality can acheived by using ACE Inheritance in conjunction with changing the Registry setting for "KeepInheritance" to enable Inheritance propagation of the Permissions by the Windows NFS Services.
1. The Precise location of the "KeepInheritance" DWORD key appears to have "moved" in Windows Server 2012 from a Services path to a Software path, is this documented somewhere? And after enabling it, (or creating it in the previous
location) the feature seems non-functional. Is there a method to file a Bug with Microsoft for this Feature?
2. All of the references on demonstrating how to set an ACE to achieve the same result "currently" either lead to broken links on Microsoft technical websites, or are not explicit they are vague or circumreferential. There are no plain Examples.
Can an Example be provided?
3. Is UUUA compatible with the method of setting ACE to acheive this result, or must the Linux client mount be "Mapped" using an Authentication source. And could that be with the new Flat File passwd and group files in c:\windows\system32\drivers\etc
and is there an Example available.
Scenario:
Windows Server 2012 Standard
File Server (Role)
+- Server for NFS (Role) << -- installed
General --
Folder path: F:\Shares\raid-6-array
Remote path: fs4:/raid-6-array
Protocol: NFS
Authentication --
No server authentication
+- No server authentication (AUTH_SYS)
++- Enable unmapped user access
+++- Allow unmapped user access by UID/GID
Share Permissions --
Name: linux_nfs_client.host.edu
Permissions: Read/Write
Root Access: Allowed
Encoding: ANSI
NTFS Permissions --
Type: Allow
Principal: BUILTIN\Administrators
Access: Full Control
Applies to: This folder only
Type: Allow
Principal: NT AUTHORITY\SYSTEM
Access: Full Control
Applies to: This folder only
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

I'm making some "major" progress on this problem.
1. Apparently the "semantics" issue to honor SGID or grpid in NFS on the server side or the client side has been debated for some time. It also existed as of 2009 between Solaris nfs server and Linux nfs clients. The Linux community defaulted to declaring
it a "Server" side issue to avoid "Race" conditions between simultaneous access users and the local file system daemons. The client would have to "check" for the SGID and reformulate its CREATE request to specify the Secondary group it would have to "notice"
by which time it could have changed on the server. SUN declined to fix it.. even though there were reports it did not behave the same between nfs3 vs nfs4 daemons.. which might be because nfs4 servers have local ACL or ACE entries to process.. and a new local/nfs
"inheritance" scheme to worry about honoring.. that could place it in conflict with remote access.. and push the responsibility "outwards" to the nfs client.. introducing a race condition, necessitating "locking" semantics.
This article covers that discovery and no resolution - http://thr3ads.net/zfs-discuss/2009/10/569334-CR6894234-improved-sgid-directory-compatibility-with-non-Solaris-NFS-clients
2. A much Older Microsoft Knowledge Based article had explicit examples of using Windows ACEs and Inheritance to "mitigate" the issue.. basically the nfs client "cannot" update an ACE to make it "Inheritable" [-but-] a Windows side Admin or Windows User
[-can-] update or promote an existing ACE to "Inheritable"
Here are the pertinent statements -
"In Windows Services for UNIX 2.3, you can use the KeepInheritance registry value to set inheritable ACEs and to make sure that these ACEs apply to newly created files and folders on NFS shares."
"Note About the Permissions That Are Set by NFS Clients
The KeepInheritance option only applies ACEs that have inheritance enabled. Any permissions that are set by an NFS client will
only apply to that file or folder, so the resulting ACEs created by an NFS client will
not have inheritance set."
"So
If you want a folder's permissions to be inherited to new subfolders and files, you must set its permissions from the Windows NFS server because the permissions that are set by NFS clients only apply to the folder itself."
http://support.microsoft.com/default.aspx?scid=kb;en-us;321049
3. I have set up a Windows 2008r2 NFS server and mounted it with a Redhat Enteprise Linux 5 release 10 x86_64 server [Oct 31, 2013] and so far this does appear to be the case.
4. In order to mount and then switch user to a non-root user to create subdirectories and files, I had to mount the NFS share (after enabling Anonymous AUTH_SYS mapping) this is not a good thing, but it was because I have been using UUUA - Unmapped Unix
User Access Mapping, which makes no attempt to "map" a Unix UID/GID set by the NFS client to a Windows User account.
To verify the Inheritance of additional ACEs on new subdirectories and files created by a non-root Unix user, on the Windows NFS server I used the right click properties, security tab context menu, then Advanced to list all the ACEs and looked at the far
Column reflecting if it applied to [This folder only, or This folder and Subdirectories, or This folder and subdirectories and files]
5. All new Subdirectories and files createdby the non-root user had a [Non-Inheritance] ACE created for them.
6. I turned a [Non-Inheritance] ACE into an [Inheritance] ACE by selecting it then clicking [Edit] and using the Drop down to select [This folder, subdirs and files] then I went back to the NFS client and created more subdirs and files. Then back to the
Windows NFS server and checked the new subdirs and folders and they did Inherit the Windows NFS server ACE! - However the UID/GID of the subdirs and folders remained unchanged, they did not reflect the new "Effective" ownership or group membership.
7. I "believe" because I was using UUUA and working "behind" the UID/GID presentation layer for the NFS client, it did not update that presentation layer. It might do that "if" I were using a Mapping mechanism and mapped UID/GID to Windows User SIDs and
Group SIDs. Windows 2008r2 no longer has a "simple" Mapping server, it does not accept flat text files and requires a Schema extension to Active Directory just to MAP a windows account to a UID/GID.. a lot of overhead. Windows Server 2012 accepts flat text
files like /etc/passwd and /etc/group to perform this function and is next on my list of things to see if that will update the UID/GID based on the Windows ACE entries. Since the Local ACE take precedence "over" Inherited ACEs there could be a problem. The
Inheritance appears to be intended [only] to retain Administrative rights over user created subdirs and files by adding an additional ACE at the time of creation.
8. I did verify from the NFS client side in Linux that "Even though" the UID/GID seem to reflect the local non-root user should not have the ability to traverse or create new files, the "phantom" NFS Server ACEs are in place and do permit the function..
reconciling the "view" with "reality" appears problematic, unless the User Mapping will update "effective" rights and ownership in the "view"
-- John Willis, Facebook: John-Willis, Skype: john.willis7416

[Solved]NFS Client Not Mounting Shares

Here is my setup:
I have two Arch boxes that I am attempting to setup NFS shares on. The box that is going to be the server is headless FYI. So far, I have installed nfs-utils, started `rpc-idmapd` and `rpc-mountd` successfully on the server, and started `rpc-gssd` successfully on the client.
The folder I am trying to share is the /exports folder.
ls -l /exports
produces
total 8
drwxrwxrw-+ 110 daniel 1004 4096 Dec 6 17:26 Movies
drwxrwxrwx+ 13 daniel users 4096 Jan 8 19:12 TV-Shows
On the server:
/etc/exports
# /etc/exports
# List of directories exported to NFS clients. See exports(5).
# Use exportfs -arv to reread.
# Example for NFSv2 and NFSv3:
# /srv/home hostname1(rw,sync) hostname2(ro,sync)
# Example for NFSv4:
# /srv/nfs4 hostname1(rw,sync,fsid=0)
# /srv/nfs4/home hostname1(rw,sync,nohide)
# Using Kerberos and integrity checking:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/home gss/krb5i(rw,sync,nohide)
/exports 192.168.1.10(rw,fsid=0)
On the client:
showmount -e 192.168.1.91
Export list for 192.168.1.91:
/exports 192.168.1.10
Everything is looking hunky-dory. However, I go to mount using
sudo mount -t nfs4 192.168.1.91:/exports /mnt/Media
and the mount never takes place. It sits there and does nothing. I CAN, however, kill the process with Ctrl-c.
So does anybody have ANY idea why my shares aren't working.
EDIT: Just thought I should mention that all of the data in the /exports folder is a mount --bind from /mnt/media. All of the /mnt/media is contained on a USB external hard drive. I did notice that there is an ACL.
getfacl /exports
getfacl: Removing leading '/' from absolute path names
# file: exports/
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
Last edited by DaBungalow (2014-01-10 03:18:05)

I found what the problem was. Apparently rpc_gssd was causing a problem. Stopping it fixed everything.

NFS client problem

Hi,
I have setuped NFS environment on solaris 9.
All the services are running in Server and Client side.
While the client rebooted im getting the mount point is not found.
like : /pani/notape is not found or does not exist.
When i umount /pani im getting mounted with some delay....
Any body tell me if any solution is there.
Thanks in advance.
Pani.

How does the client mount the share -- you use automount maps or just an entry in vfstab? Did you try snooping the traffic to see if the client is at least attempting to mount the share?

Normal NFS client reaction when connection lost then re-established

Say I have an NFS share mounted with defaults. There is no outstanding IO to the share and the server goes down. The server comes back up and there is an attempt to access the share. What should happen when this attempt is made? It seems to me that it should be like the server never went down. Instead, things behave more like the server never came back up: any application attempting to access it hangs indefinitely.
Using the mount option 'soft' prevents this from happening, but it doesn't seem like one should have to risk 'silent data corruption' to prevent the client from going completely stupid when it loses contact for a period that no contact should be necessary.

This is HIGHLY unrecommended. The NFS protocol has never, and probably will never, highly robust. VPN tunnels are prone to latency issues and session drops as a result. For this reason smb or afp or any form of FTP or sFTP is far more safe and reliable. All of these other protocols have mechanisms for reestablishing a session lost due to latency, unlike NFS. Additionally, NFS is sufficiently embedded in most UNIX kernels to potentially lock or crash the NFS client when a session goes stale. More recent versions of many OS's, including Solaris 9, have overcome the crash conditions usually caused, but at the expense of NFS filesystem integrity...

NFS client question ... do I need rpc?

Hi All!
I am in the process of doing some security auditing and in the process I came across open rpc ports that I believe I don't actually need. I would like to solicit thoughts on this:
I have solaris 8 and 10 machines importing NFS filesystems from a solaris 8 server. For the client machines, is there any reason to have rpc running?
I tested this with a solaris 8 machine, turned off both lockd/statd (/etc/init.d/nfs.client stop) and rpc (/etc/init.d/rpc stop), made sure that the daemons were not running and tried to nfsmount a share on the client:
mount -F nfs server:/share /mnt/tmp
which seemed to work fine. So do I need lockd/statd and rpc or not?
Rudolf

As I said, I tested the ability to connect to NFS even in the absence of rpc / lockd / statd on the client. However, it seems mAbrante is right about these services being at least advisable on the client to allow file locking. This is an excerpt from the lockd manpage that I should have spotted before even asking this question:
State information kept by the lock manager about these locking requests can be lost if the lockd is killed or the operating system is rebooted. Some of this information can be recovered as follows. When the server lock manager restarts, it waits for a grace period for all client-site lock managers to submit reclaim requests. Client-site lock managers, on the other hand, are notified by the status monitor daemon, statd(1M), of the restart and promptly resubmit previously granted lock requests. If the lock daemon fails to secure a previously granted lock at the server site, then it sends SIGLOST to a process.
So I guess you don't need the rpc / lockd / statd but you will lose functionality ... you might be able to get away with it if the exported filesystem is read only ...
Rudolf

Ports needed for a nfs client

Hello -
Which ports on a firewall running on a solaris 10 machine should I open to make it a nfs client? I openned udp/tcp port 111. But it didn't work. The file server is running solaris 9.
Thanks
Rui

If you use the WebNFS feature of Solaris it will only require port 2049, to use WebNFS, simply mount your NFS share as an URI.
For example, replace:
mount server:/share /mountpoint
with
mount nfs://server/share /mountpoint
.. to use WebNFS instead.
.7/M.

Svc:/network/nfs/client problem in Solaris 10

Hi,
I`ve been trying to figure out what is the problem with the below scenario for so long and till now i`m not able to.
i have a X4100 SunFire system with solaris 10 installed.
most of the services are not coming up (ssh,ftp,etc....) each time i reboot the server, and after approximately 3 hours everything comes fine by it self.
i noticed that the service :/network/nfs/client is taking too long while starting. This might be related to the problem.
See below the svcs command : hope this will be usefull :)
bash-3.00# svcs -xv ssh
svc:/network/ssh:default (SSH server)
State: offline since Wed May 20 16:37:45 2009
Reason: Service svc:/network/nfs/client:default is starting.
See: http://sun.com/msg/SMF-8000-GE
Path: svc:/network/ssh:default
svc:/system/filesystem/autofs:default
svc:/network/nfs/client:default
See: man -M /usr/share/man -s 1M sshd
Impact: 3 dependent services are not running:
svc:/milestone/multi-user-server:default
svc:/system/basicreg:default
svc:/system/zones:default
any advise on this ?
Appreciate your help,

hi all
issue resolved actually port was conflicting in /etc/services i have readded the entry in /etc/service
Thanks

Problems enabling nfs client and server

I just re-build a solaris 11.1x86 on a x4640 SunFire
Have problems enabling nfs
First i typed the following command:
# svcs network/nfs/server
disable
Second I typed the following command:
#svcadm enable network/nfs/server
# svcs network/nfs/server
offline
did this 3 or 4 times without success...
any ideas?
I holding production here! Please help!!

Let's rule out the easier stuff first...
Do you have something shared?
I think you need to have something shared before you can enable the nfs server service.
Or, if you share something, the service is started automatically. See below.
Thanks, Cindy
# svcs -a | grep nfs
disabled Feb_26 svc:/network/nfs/client:default
disabled Feb_26 svc:/network/nfs/server:default
disabled Feb_26 svc:/network/nfs/rquota:default
# svcadm enable svc:/network/nfs/server:default
# svcs | grep nfs
disabled 13:51:52 svc:/network/nfs/server:default
# zfs set share.nfs=on rpool/cindy
# share
rpool_cindy /rpool/cindy nfs sec=sys,rw
# svcs | grep nfs
online Feb_26 svc:/network/nfs/fedfs-client:default
online Feb_27 svc:/network/nfs/status:default
online Feb_27 svc:/network/nfs/cbd:default
online Feb_27 svc:/network/nfs/mapid:default
online Feb_27 svc:/network/nfs/nlockmgr:default
online 13:52:35 svc:/network/nfs/rquota:default
online 13:52:35 svc:/network/nfs/server:default

Wrong atime created by iMac as a NFS client

We have iMac computers in classrooms, and they are running as an NFS client. We have found that the wrong access time (atime) is created by Mac OS 10.5 and 10.6.
A file that is opened by using O_CREATE on the NFS-mounted directory will have the wrong atime. For example, the year will appear as 1920 or 2037 depending on the IP address of the NFS client.
This problem can also be found with Solaris NFS server and EMC Celerra.
The following program will create a file having the wrong atime on an NFS-mounted directory:
#include <fcntl.h>
#include <stdlib.h>
#include <string.h>
#include <stddef.h>
main() {
int fd;
/* O_EXCL option will cause wrong atime */
fd = open("AIZU", O_CREAT | O_EXCL | O_RDWR, 0644);
/* fd = open("AIZU", O_CREAT | O_RDWR, 0644); */
close(fd);
exit(0);
The phenomenon is quite similar to the following problems on FreeBSD reported in 2001:
http://www.mail-arch...g/msg22084.html
If anyone knows a solution to this problem, we would greatly appreciate your advice. Thanks in advance.

The solution shown in
http://www.mail-archive.com/[email protected]/msg22084.html
should be applied to the current NFS modules of Snow Leopard.

Is NFS client data cacheing possible?

Yesterday, I was viewing an HD 1080 video with VLC, and noticed that Activity Monitor was showing about 34MB/sec from my NAS box. My NAS box runs OpenSolaris (I was at Sun for over 20 years, and some habits die hard), and the 6GB video file was mounted on my iMac 27" (10.7.2) using NFSv3 (yes, I have a gigabit network).
Being a long term UNIX performance expert and regular DTrace user, I was able to confirm that VLC on Lion was reading the file at about 1.8MB/sec, and that the NFS server was being hit at 34MB/sec. Further investigation showed that the NFS client (Lion) was requesting each 32KB block 20 times!
Note: the default read size for NFSv3 over TCP is 32KB).
Digging deeper, I found that VLC was reading the file in 1786 byte blocks. I have concluded that Lion's NFSv3 client implement at least one 32KB read for each application call to read(2), and that no data is cached betweem reads (this fully accounts for the 20x overhead in this case).
A workaround is to use say rsize=1024, which will increase the number of NFS ops but dramatically reduce the bandwidth consumption (which means I might yet be able to watch HD video over wifi).
That VLC should start issuing such small reads is a bug, so I have also written some notes in the vlc.org forums. But client side cacheing would hide the issue from the network.
So, the big question: is it possible to enable NFS client data cacheing in Lion?

The problem solved itself mysteriously overnight, without any interference from myself.
The systems are again perfectly happily mounting the file space (650 clients of them all at the same time
mounting up to 6 filesystems from the same server) and the server is happily serving again as it has been for the past 2 years.
My idea is that there has been a network configuration clash, but considering that the last modification of NIS hosts file was about 4 weeks ago and the latest server was installed then and has been serving since then, I have no
idea how such clash could happen without interference in the config files. It is a mystery and I will have to make
every effort to unravel it. One does not really like to sweep incidents like that un-investigated under the carpet.
If anybody has any suggestions and thoughts on this matter please post them here.
Lydia

NFS client test program

I'm trying to write a test program that behaves like an NFS client. The code uses the standard RPC calls to talk to the NFS server. It compiles and runs fine on Linux. On Solaris though I have a problem establishing an RPC client initially.
The test program performs the following operations:
1. Uses the portmapper service on the server to establish the remote port associated with the MOUNT service
1. Creates a socket, sockfd.
2. Uses bindresvport to bind a reserved port to the socket. The port number is in the reserved range (ie 600 to 1000ish).
3. Connects this socket to the server
3. Creates a struct sockadd_in with the appropriate address information for the server in addr
4. Calls clnttcp_create
The following code
client = clnttcp_create(addr, <------- points at the server
program, <-------- MOUNT RPC program number
program_version, <--------- MOUNT RPC program version
&sockfd, <------- connected socket using a reserved port on the local client
0,
0);
if (client == NULL) {
clnt_pcreateerror("clnttcp_create");
returns "clnttcp_create: RPC: Remote system error - Address already in use".
So it looks like port 688 (the local port selected say by bindresvport) is already in use ? But that's the whole point, I need to provide cnttcp_create() with a socket that already has a port bound to it.
The same code runs fines on a Suse 11 client talking to Open Solaris 11 server. The same code run as a client on Solaris 11 fails with the above message when talking to either a Suse 11 server or a Solaris 11 server.
Any suggestions what I'm doing wrong? Is this the right forum in which to ask?
many thanks

Make sure you have the sub-folder com, and then another sub-folder underneath it, mastertech and another sub-folder underneath this called sample. This is how packages are structured. They should be in your ep workspace directory structure if you're using Eclipse. In JBoss, you do not have to have the packages or any source code structure. Just jar your compiled code and save in JBoss's deploy folder which only accepts jar's, war's and ear's.

PROBLEM: Filemaker Server is ROOT and ROOT can't see mounted shares

We have Filemaker server 8 running on our machine and have found a silly problem. Filemaker has a built in tool to backup databases. Databases can be backed path can be over the network by typing:
filemac:/[volume]/[path]
Unfortunately, the process "Filemaker" is owned by ROOT, while the server (another OSX server) is owned by the user "filemaker". In theory ROOT is god, and can do anything, but for some reason ROOT doesn't appear to be able to get to shares owned by a user on the machine. Can anyone help me with any of the following potential sollutions?
1) Mount a share on startup as ROOT
2) Allow ROOT read/write to shares that other users have mounted
3) Change "ownership" of the "Filemaker" proccess to be a user (instead of ROOT)
Worse case I could back up the files locally, and then create an applescript to PUSH the files where they're supposed to live, but that feels like one more thing that could go wrong to me, and I like to have as few moving parts as possible.
Thanks in advance

This is incorrect, Filmaker Server is not "ROOT" and you probably won't have much satisfaction pursuing your line of thinking.
ps -aux | grep -i filemaker
fmserver 457 3.0 -2.5 186340 53236 ?? Ss 19Mar06 316:56.83 /Library/FileMaker Server/Tools/fmserverd
fmserver 431 1.1 -0.4 93736 8576 ?? Ss 19Mar06 179:51.17 /Library/FileMaker Server/Tools/fmserver_helperd
I think you may be confusing the parent process with posix user/group permissions. Yes, the parent process of many running processes will show as "root", because the initial process that launches others runs as/belongs to root.
the "root" user in *nix has full permissions and can see mounted shares. You may have some other issues due to misconfiguration, sorry.
Just in case you are doing so, no matter what anyone tells you anywhere, it is not a good idea to log in as "root" via the GUI (when the server finishes booting and asks for a username and password).
One should not do this for a number of reasons.
As for your FM Server problem, I've done two migrations/updates to FM 8 server & client quite recently.
The installation creates a new system user and group, which you will not see without selecting the "show system users" in Workgroup Manager.
The user (ie: owner) is (shortname) fmserver , and the group is fmsadmin
FM Server stores the working databases in /Library/FileMaker Server
and that "FileMaker Server" directory is owned by fmserver:fmsadmin
You should not change that or FM won't run properly, if at all.
You can point to whatever directory you wish, using FM Server's built-in backup automation.
What is probably throwing you off, is that, unless you put a trailing slash at the end of the path you enter (in the dialog for the FM Server built-in backup routine), it will tell you:
"invalid path"

What causes the automatic unmount of mounted shares?

Hi all,
I was wondering what would cause a share to automatically unmount...
Let's say I mount 3 shared folders located in 3 different machines on my LAN (AFP shares).
"SharedFolder1" is on "Machine1"
"SharedFolder2" is on "Machine2"
"SharedFolder3" is on "Machine3"
From "Machine0" I can read and write the content of all the shared folders.
However, when I come back the next morning, only "SharedFolder2" is mounted (on "Machine0") and I get no error message (at least none that is still visible). I can remount "sharedFolder1" and "SharedFolder3", but I was wondering why these were unmounted on "Machine0"... All I know is that "Machine1" and "Machine3" didn't reboot nor shut down...
Maybe it is a setting on "Machine1" and "Machine3", respectively?
Maybe they went to sleep?
Maybe this is due to user switching on the remote machine?
Maybe there's a time limit where an idle mounted share would be automatically unmounted?
I don't know, there are so many settings... and I could run a lot of tests to figure it out...
Does anyone know what can cause a share to be unmounted?
Thank you very much in advance for your help.
Best,
-a-

"Since I recently bought a Time Capsule, I set up a sharing volume with my wife's computer. I set wake on demand and it works perfectly. Even putting her computer to sleep and mine gone to sleep, the volume stays mounted. When I wake mine up, the shared folder from her computer ejects momentairly on startup, but remounts imediately after fully waking. Her computer is still in sleep mode."
     Exactly the behavior I would be expecting...
     Although I would also expect a password prompt if it is not stored
     in the client...
"So, to answer you question, if wake on demand is set up correctly on the shared computer, the shared folder does not eject when putting shared computer in sleep mode.
But, if the sharing computer looses power or wake on demand is not set or working correctly, it will disconnect and eject the volume."
     This is what I get right now, but different shares
     (different remote machines)
     behave differently, some of them unmount, while other
     remain mounted...
     I can't find out what the difference is among their respective settings.
"Apple says it requires an Airport Airport Base Station or Time Capsule with up to date firmware for wake on demand to work, so I don't know if any other router today will support that feautre for Apple. I know for sure my older router did not have the capability and I could never find a work around."
     Why the heck to they ALWAYS do that?!?
     Whatever... Thank you very much for your answer anyway.
     Happy Holiday
     -a-

Systemd nfs client mount share ???

Similar Messages

Maybe you are looking for