Mac OS X Catalina - NFS File Access Behavior in CRON or Launchd Post: 303045436

Sponsored Content

Top Forums UNIX for Beginners Questions & Answers Mac OS X Catalina - NFS File Access Behavior in CRON or Launchd Post 303045436 by bminear on Friday 20th of March 2020 04:59:56 PM

03-20-2020

Registered User

Quote:

Agreed. Also, check the access rights set on the NAS end. I'm no MAC user either but perhaps your upgraded OS is checking acess rights on the NAS that it wasn't checking before.

Well, I'm about to give up. I've gone through every single permission and access rights option on the NAS, no luck. Again, what completely confuses me is that I can run the script manually from the shell and everything works perfectly. So I know that the NFS directory is mounted, and that root user can read the files in it. But as soon as it's a cron job or a launchd job that runs the script it can see the file, but can't read it.

The log simply says:

Code:

cat: /System/Volumes/Data/nfs/hosts: Operation not permitted

Without a doubt the upgrade to Catalina resulted in scripts being run within the context of cron or launchd to use a different environment than that of the command line. This approach of mine works on ALL my other Linux, *nix (SunOS, Solaris, HP-UX, AIX, Linux), heck, even OpenVMS, but no longer on Mac OS X. Grrrrr....

bminear

View Public Profile for bminear

Find all posts by bminear

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Strange IP traffic behavior when using Samba and FTP (Windows/Mac to Linux)

I have set up a samba share on my Linux server. I have a gigabit switch, gigabit NICs in each machine. I have set up the /etc/samba/smb.conf to support no delay, 8192 send/receive buffers, etc. This helped the rate for Samba go from about 4MB/S to about 10MB/S, but I expect to see about...

2. AIX

Cannot access NFS file system

I create a NFS file system. I can read this system from client, however, I cannot write anything in this folder. Why?

3. Shell Programming and Scripting

Behavior of Bad Script in Cron Job

Hi A Ksh script is deployed in a server and executed through cronjob. If one of the line in the middle of the script fails . Are the remaining lines executed ?

4. Red Hat

NFS Access Issue

Hi, I am facing issue on NFS. I have shared /data file file system on Server 192.192.192.1, added below lines in /etc/exports /data 192.192.192.2(rw,no_root_squash,sync) the owner of /data directory was test(uid 500) and same I have mounted on another server 192.192.192.2 where the...

5. Shell Programming and Scripting

grep startup messages from catalina.out file

Hello Team, I am trying to extract date from the following output and trying to compare with current date and if there is 10 minute difference between the two. it should logs message in the file server is started.can anyone help me to implement this in the script?

6. UNIX for Advanced & Expert Users

Different redirection behavior in BASH/Linux when run under cron vice login ???

run_xfs_fsr is a xfs filesystem maintenance script designed to run under cron. The system is a home theater personal computer running mythbuntu 10.10, and is accessed remotely for these tests. cron runs a script, (xfs_fsr.sh) at 02:30 that runs the subject script under BASH and sets the...

7. UNIX for Dummies Questions & Answers

Launchd-owned processes unexpected behavior

Ok, so I have been struggling with this for a few days and I think I need an explanation of a few things before I go any further. I'm not sure it's possible to do what I'm trying, so before I pull my hair out, here is what I'm doing: I have written a program in LiveCode that sits on our...

LEARN ABOUT SUNOS

unshare_nfs

unshare_nfs(1M) 					  System Administration Commands					   unshare_nfs(1M)

NAME

       unshare_nfs - make local NFS file systems unavailable for mounting by remote systems

SYNOPSIS

       unshare [ -F nfs] pathname

DESCRIPTION

       The  unshare  command makes local file systems unavailable for mounting by remote systems. The shared file system must correspond to a line
       with NFS as the FSType in the file /etc/dfs/sharetab.

OPTIONS

       The following options are supported:

       -F	This option may be omitted if NFS is the first file system type listed in the file /etc/dfs/fstypes.

FILES

       /etc/dfs/fstypes

       /etc/dfs/sharetab

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWnfssu 		   |
       +-----------------------------+-----------------------------+

SEE ALSO

       nfsd(1M), share(1M), attributes(5)

NOTES

       If the file system being unshared is a symbolic link to a valid pathname, the canonical path (the path which  the  symbolic  link  follows)
       will be unshared.

       For  example,  if  /export/foo is a symbolic link to /export/bar (/export/foo -> /export/bar), the following unshare command will result in
       /export/bar as the unshared pathname (and not /export/foo):

       example#  unshare -F nfs /export/foo

       For file systems that are accessed by NFS Version 4 clients, once the unshare is complete, all NFS Version 4 state  (open  files  and  file
       locks)  are  released and unrecoverable by the clients. If the intent is to share the file system after some administrative action, the NFS
       daemon (nfsd) should first be stopped and then the file system unshared. After the administrative action is complete, the file system would
       then be shared and the NFS daemon restarted. See nfsd(1M)

SunOS 5.10							    6 May 2003							   unshare_nfs(1M)