I have java 7 and Java 8 installed in this machine, but I set the execution environment and the compiler compliance level to java 7. jar files that OS X installed in /System/Library/Java/Extensions. jar files in the eclipse plugin folder with the most recent versions for JGL, but all that happens is that the message changes to something like:ģD 1.6.0-pre11-daily-experimental daily The 3D models run even if I cannot see the 3D graphics, as clicking randomly on the grey screen sometimes opens the agent inspector pane. The only message left in the console when this happens is:ģD 1.6.0-pre9-daily-experimental daily The problem is that all 3D displays are grey. dmg file, and have succeeded in running all example models without any error.
#MESSAGE MACOS SHARE SCREEN GREYED OUT MAC OS#
The reason for wanting SMB access only to the archive area is that there are multiple client types that can access it some of which are old Windows machines that don't have particularly good NFS client implementations.I installed Repast Simphony from the Mac OS X. It is slightly antiquated but the team in question have found that it works for them So in the end we only retain one copy of the data so no really happy salesman. The original location is the working area of the entire team in question, once the work is complete the data is then archived (copied to the a new location) and once secure and verified is then deleted from the original working location. The data is copied from one location to another for archiving. I have reverted to exposing the new location via NFS and allowing certain clients only to mount to allow the copying process
Reverting to SMB1 didn't seem to make any difference the copied files still remain greyed out in the finder window yet are accessible from a Windows machine or over NFS in the new locationīeginning to find the SMB from the MAC has a few interesting challenges As is Apple tradition, they say "they are aware" but refuse to reveal a fix date or release vehicle. Numerous bugs seen by the community, several not fixed by Apple. Having said that, you may have very good reason to duplicate content - so carry on, but again beware of 10.9.x with SMB2. Now, I'm sure your Isilon rep is delighted that you are consuming 2x the space on your cluster but it's entirely unnecessary just to access the same files. If you need SMB access from a Mac running 10.9.x, it may be worth your while to revert to SMB1, or ignore SMB completely and run NFS.īut I am curious why you are copying files from an NFS export to an SMB share at all - why not just expose the same Isilon directory via SMB to the same host that has the NFS export, instead of copying data? Many Isilon users expose the same directory via several protocols simultaneously. There are bugs aplenty, even in 10.9.2, some of which directly affect SMB shares and files' behavior. Several things going on here.first, beware of the SMB2 stack on Mountain Lion (10.9.x). I am thinking of making the SMB share accessible via NFS and then doing a copy from NFS share to NFS share to see if that fixes it
#MESSAGE MACOS SHARE SCREEN GREYED OUT HOW TO#
Has anyone seen this behaviour before or have any idea how to get round it. These ACLs exist on both the source and destination files, and I can access the source file from both NFS and SMB mountsĪCLs shown below for both Domain user and the local NFS user that has accessĠ: user:DOMAIN\craign allow inherited dir_gen_read, dir_gen_write, dir_gen_execute, std_delete, std_write_dac, delete_child, object_inherit, container_inherit,inherited_aceġ: user:print allow inherited dir_gen_read,dir_gen_write,dir_gen_execute,std_delete,object_inherit,container_inherit,inherited_ace
I have looked at the ACLs on the directory involved and it seems to have the correct setting to allow me access (which I can from Windows 7) Basically I think that Finder is not completing so it tidys up after itself and removes the copied files
If I SSH to the Isilon and check the directory I can see files in it and if I mount the SMB share on a Windows box again I can see the files with the correct date informationġ0.8 - The copy progresses as expected and the files appear on the Isilon but at the end of the process the files are deleted again. The copy starts and then depending on the version of MAC OS the following happensġ0.9 - The copied directory is greyed out in SMB share window and the modified date on the directory is set to 24 January 1984. I am copying directories from an NFS share to a SMB share on the same Isilon cluster using the MAC finder to copy/paste
0 kommentar(er)
