File locks problem

We get the following error message from our UBB version 6 message board software, running under Solaris 8:
Can't EXlock '/content/nfs/www.granadabroadband.net/messages/trisha/cache-xxxxxxx/lock/global.cgi'. The operating system has run out of file locks to give me. Please ask the administrator to contact the web hosting provider. The exact error returned by the operating system is: No record locks available
We would like to increase the size of the system file lock table and there seems to be a kernel setting called nflocks that does this. However, we cannot find any information about how to set the value of nflocks ourselves.
Can anyone advise us please?

Pls. check this url for this query:
http://docs.sun.com/db/doc/802-5750/6i9g464qu?a=view
Section :
How to Increase the Number of Lock Requests
Senthilkumar

Similar Messages

Problem Loading pdf using AxInterop.AcroPDFLib (file locked)

Hi,
I'm currently using AxInterop.AcroPDFLib with C# in a winform application.
Purpose is to display PDF files in my application. Thoose files are located on a share directory.
Everything works fine, the program is installed on multiple pc that display the file at the same time without problem.
BUT, when i open the same PDF file on a computer using acrobat pdf reader, i can't open the same file using the AxInterop.AcroPDFLib dll.
After some deep search on the files, on the servers, ... it seems to be linked with file locking.
Let me explain :
when the file is opened by the AxInterop.AcroPDFLib dll, no lock appears on the server ( share directory ) or at least it appears and is released in the same second.
when i open the PDF file via acrobat reader, the lock is set, and remain until i close the file in the pdf reader.
which means that when someone open a file, all the computer using the AxInterop.AcroPDFLib ares blocked and can't start reading the file.
Is there a way to configure the AxInterop.AcroPDFLib to allow reading on locked files (locked for reading)
Thanks
Mike

I have tried with both Reader 8.xx and 9.xx
Same behavior.
After deep investigation, i have found that when i open a file using the reader, this file is marked as opened for "read" on the server, and in that case, the ocx can't open the file...
when the file is close by the reader, the lock is removed and the ocx could open the document.
I found also that when the ocx open the file, this file is not locked on the server, which allows other computers with the same ocx to open the same file on multiple workstation (which is the behavior i was expecting).
thus why is the ocx blocked when a file lock is present on the server for the file to be opened by the ocx...
Mike

File access/locking problems, most notably with AutoCAD

A number of sporadic problems of AutoCAD users who've been working away
suddenly not able to write to the file they've been working on. If
multiple people try to use the same Xrefs, often some will get that the
file is corrupted report by AutoCAD.
What is reproducible is one of the Xref problems and it has given us a
bit of a work around to keep working.
To Reproduce:
Start AutoCAD(2009), open a file with base(Xref)
Save the base (no change needed) without closing, and refresh
the base disappears from view, and when we look in the 'Xref Manager'
we see that the Base has a status of 'Needs Recovery'. This applies
even when multiple people had the Xref in read only view, that it is
now unavailable, but when the full drawing is shut down and reopened
by the one who had saved, the Xref is just fine.
Autosave is not triggering the problem.
This has been reproduced on the newest version of ACAD as well, just
slightly different wording of errors.
OES2 sp3 servers (in VMWare) with mostly XPsp3 clients but a few
Windows 7 ones as well. The clients mostly have the newest clients
installed, but there are some of the XP boxes with 4.91.4 still on
them.
Just migrated the main data volume from NetWare 6.5.8 to OES2 Linux and
immediately started having the problem. 100% of file access is via
NCP. no CIFS is configured, to the point we have cross-protocol-locks
set to 0 (Zero, i.e. Off).
I think I've been through every combination of file locking settings of
server vs workstation without any apparent change.
Still working out different tests to do to find what makes a
difference.
Observations that might just lead to clues toward the root cause:
- On NetWare, if a user left files open over night, we could still see
those being listed as opened in Monitor. Past history with these users
is that there was always several showing as open every night even when
we were sure they'd all been gone for hours. Now when we check the all
the volumes late in the evening, they've been showing no files open.
perhaps that is a clue to a problem in lock tracking.
- While still at OES2 sp2, the pilot team kept giving vague
descriptions of problems using ACAD against files on OES2, but those
all went away after applying SP3, so after 2 months of one small group
running ACAD against files stored on OES2-linux, we migrated the bulk
of the data as the last volume from a failing NetWare 6.5.8 cluster
(recreating SBDs was getting tiring).
Andy Konecny
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

Originally Posted by HvdHeuvel
On Tue, 19 Jul 2011 14:19:33 +0000, Andy Konecny wrote:
> In article <NvZTp.3150$[email protected]>, Hans van den
> Heuvel wrote:
>> This sounds as bug #691870
>>
> yup, it is, and that bug has actually been marked as a duplicate of
> another and has been merged. The other related to opening and saving
> PDF files, which we were also hitting as well. One user who had to
> generate many PDFs off of a set of drawings was particularly nailed by
> this.
>
> I have the FTF and applied it last night, just had to chase a few
> stragglers to take a break to activate it since doing so does briefly
> break links (reports/broadcasts as server 'down', but only for a
> minute). The users are much happier this morning, got very nice
> greetings as I arrived on-site. So far no sign of any other related
> issues.
Glad to hear that your (and our) customer's life became less complicated.
Keep up doing the good work !
Best regards
Hans
Hi Hans,
i have just helped a customer to migrate their data from NW65SP8 to OES2SP3 and hit the same problem with the CAD group using AutoCAD 2004 on Windows XP with NC491SP3 + some Postpatches
Do we have a release date for the next OES2 SP3 Scheduled Maintenace Patch?
The last available is from May and has been apparently released the 31st of May.
Do we have a chance to get the ftf in someway?
Many thanks in advance and best regards,
Stefano Barello
LANworks AG - IT Engineering

Fireworks CS 6 Launch problem - File locked

This message comes up for pupils on our network after the splash screen.
Fine for teachers.
Pupils can launch Photoshop without problems.
Solutions?

Our setup:
- Windows 2008 R2 servers
- Windows 7 client
Other components of the CS6 suite work fine under the pupil log in
Fireworks works fine as a teacher.
For a pupil launching Fireworks you see the splash screen, the error box with 'file locked' - no indication where the application is trying to write to.
Currently a tiny needle in a haystack.
Thank you for your reply Mylenium. Any further thoughts?

File lock() method problem

I know this may be a common question, but can someone explain why this code:
import java.io.*;
import java.nio.channels.*;
import java.util.*;
public class TestFileLock
     private static File file;
     private static RandomAccessFile fileRandom;
     private static FileChannel fileChannel;
     private static FileLock fileLock;
     private static String process;
     public static void main(String[] args)
          process = args[0];
          try
               file = new File("/home/fauxn/work/blast/java/java_blast/test.log");
               //fileWriter = new FileWriter(file, true);
               fileRandom = new RandomAccessFile(file, "rw");
               fileChannel = fileRandom.getChannel();
               for(int i =0; i < 1000; i++)
                    writeLogFile(process + ": happy days\n");
          catch(Exception exception)
               System.out.println(exception.getMessage());
               exception.printStackTrace();
     * Method lockes the logFile and then append the string to the file and unlocks the file.
     * @author Noel Faux.
     * @param s The string to be written to be appended to the file.
     private static void writeLogFile(String s) throws IOException
     System.out.println(process + ": trying to lock the log file");
     fileLock = fileChannel.tryLock();
     while(fileLock == null)
               System.out.println(s + ": waiting!!!!");
               fileLock = fileChannel.tryLock();
     System.out.println(s + ": logfile locked");
          fileRandom.seek(fileRandom.length());
     fileRandom.write(s.getBytes());
          fileLock.release();
          System.out.println(s + ": logfile unlocked");
produces this error:
Invalid argument
java.io.IOException: Invalid argument
at sun.nio.ch.FileChannelImpl.lock0(Native Method)
at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:528)
at java.nio.channels.FileChannel.tryLock(FileChannel.java:967)
at TestFileLock.writeLogFile(TestFileLock.java:43)
at TestFileLock.main(TestFileLock.java:23)
on a intel linux box, java 1.4 and this code works fine:
import java.io.*;
import java.nio.channels.*;
import java.util.*;
public class TestFileLock
     private static File file;
     private static RandomAccessFile fileRandom;
     private static FileChannel fileChannel;
     private static FileLock fileLock;
     private static String process;
     public static void main(String[] args)
          process = args[0];
          try
               file = new File("/home/fauxn/work/blast/java/java_blast/test.log");
               //fileWriter = new FileWriter(file, true);
               fileRandom = new RandomAccessFile(file, "rw");
               fileChannel = fileRandom.getChannel();
               for(int i =0; i < 1000; i++)
                    writeLogFile(process + ": happy days\n");
          catch(Exception exception)
               System.out.println(exception.getMessage());
               exception.printStackTrace();
     * Method lockes the logFile and then append the string to
* the file and unlocks the file.
     private static void writeLogFile(String s) throws IOException
     System.out.println(process + ": trying to lock the log file");
     fileLock = fileChannel.tryLock(0, fileRandom.length(), false);
     while(fileLock == null)
               System.out.println(s + ": waiting!!!!");
               fileLock = fileChannel.tryLock(0, fileRandom.length(), false);
     System.out.println(s + ": logfile locked");
     fileRandom.seek(fileRandom.length());
     fileRandom.write(s.getBytes());
     fileLock.release();
     System.out.println(s + ": logfile unlocked");
Any suggestions welcome, or is this a bug????
Thanks in advance :)

Its a known bug. The default tryLock() method calls the parametered
tryLock method as follows
tryLock(0,Long.MAX_VALUE,false);unfortunately under linux the parameter Long.MAX_VALUE is too big for
the underlying OS file locking. This causes the IOException to be thrown
It has been fixed in version 1.4.1 i believe.
For more info
http://developer.java.sun.com/developer/bugParade/bugs/4532474.html
matfud

Help! File locking/multi-thread/instance problem!

Hi,
I have a program which runs multiple threads and they call a seperate java class to write information to a file. However because there are many threads some of the information sometimes gets lost. Unfortunately I am restricted to Java 1.1 so cannot use file locking. Does anybody know of an effective way of locking files before Java 1.4?
Alternatively it would be just as useful if only one instance of the writer class existed to write to files. Therefore is it possible for different programs/threads calling this writer class to share one instance of it so only one writer program is active thus preventing the loss of information that happens when multiple instances try to write to the same file.
Any help would be very much appreciated,
Thanks
Paul

Alternatively it would be just as useful if only one
instance of the writer class existed to write to files.
Therefore is it possible for different programs/threads
calling this writer class to share one instance of it so
only one writer program is active thus preventing the
loss of information that happens when multiple
instances try to write to the same file.This is a very good idea. Or you can implement a static method write. This, combined with syncr. will give you exactly what you need: a lock not on the file but on the writer to the file.

File locking with OSX Server & Microsoft Word

We have a small office LAN based on a Airport Extreme bases station. Periodically Microsoft Word reports a break in connection to the shared folder where we store documents to get disconnected. When that happens and the user reconnects to the share, the user gets the file read-only message for the Word document that was open at the time.
I have found that in order to clear the read-only flag, I have to restart the server and open the Word file on the server with the ID of the user who was editing the file on the remote computer. Only that seems to clear the file locking that causes the file to be read-only.
I cannot figure out a less drastic way to release the lock file. I don't see any hidden temp files in the same folder as the document that is locked for editing found by ls -a or in the root direction of the shared folder in the .TemporaryItems/folders.<UID> that seems to be holding the lock.
I have run chflags nouchg <Word file> from Terminal, but that seems to have no effect either. I also used xattr to see if there were any locks held that way, but I don't see anything that way either.
File sharing to Macs only, which are configured just to use AFP through OSX Server.
Does anyone understand how the file locks of Word documents can be released directly with out restarting the server?
I should add that the underlying problems seems to be WiFi related. The behavior is that the WiFi connection seems to break long enough that the shared volumes disconnects. Outlook also causes a break. This behavior seems to have started with 10.9 and the purchase of new Retina Display MacBook Pros. I turned off AppNap on the Office applications but that is not clearly helpful. I also have been told the problem seems more likely to occur when Word is open in the background and another program like Outlook is in the foreground.
Any suggestions appreciated.

Apple write an operating system and also produce file sharing software as part of that to be used as a file server. Apple provide documentation for third-party software developers on how they should write software to work with Apple's software and also give those developers early access to new versions so those third-party developers can test and if needed make adjustments and issue updates to cope with any Apple changes.
Some third-party developers are good at dealing with this, some are bad, and some totally ignore what Apple does and give the impression they don't care if their product works properly or not. I think we can all judge where Microsoft sits.
It appears Microsoft have never paid any attention in particular to how Apple expect file-locking to be handled when accessing files on a Mac server. There have been problems for years and years and years with Office. Two other problems I have seen which seem different to yours but probably related are -
With Office documents it is supposed to be possible for more than one person to edit the same file at the same time, consider it a miracle if this actually works
With Office in particular Word, there is an auto-save function, unfortunately the way this seems to be implemented it seems that Word creates a new temporary file each time it auto-saves the document and keeps all the previous temporary files open still, this eventually means potentially over a hundred temporary files are open - just for one Word document and you can then hit a limit on the total number of files you are allowed to have open at the same time. At this point further auto-saves fail, and you also encounter great difficulty doing a real full save of the document.
I do not hold Apple completely blameless over this issue, it is likely their file-locking implementations change too often, and have inadequate documentation, however even considering this a company the size of Microsoft with the amount of sales (and profit) they derive from Office for the Mac has no excuses at all for failing to put the effort in to resolve any such clearly critical problems.
We could go on and on about other areas where Microsoft don't play by the (software) rules. Even in Windows Office does not obey the standard print dialog rules Microsoft specified themselves!
Unfortunately not only is Office for Mac upgraded infrequently, but even when new paid for upgrades are released Microsoft have a history of still not fixing bugs. It goes without saying that a mere free update is even less likely to actually fix a bug, typically such free updates only address security issues. The next version of Office is going to be Office for Mac 2014 see http://www.macworld.com/article/2106643/microsoft-will-release-a-new-version-of- office-for-mac-this-year.html
One area I confidently predict Microsoft not to resolve in Office for Mac 2014 is that fact that Word for Mac still does not support right-to-left languages like Hebrew and Arabic. This is despite the fact that OS X itself has supported this for years and years, and despite the fact other Mac programs support this including the free TextEdit and Pages - both of which can read Word files. Some people may remember that at one point the Israeli Government temporarily banned all Microsoft software over this issue. See http://apple-beta.slashdot.org/story/03/10/15/2215249/israeli-government-suspend s-microsoft-contracts This issue goes back over TEN years!!
I note that Microsoft has now taken their OfficeForMac blog offline, probably due to the weight of criticisms. I would not say it is due to out-right anti-Microsoft hate, that war ended long ago. We just want products that work. I myself do use Microsoft products, even at home - where they are the best solution, so I use Microsoft Media Center for example. Sadly this is now being neglected by Microsoft.

File locked message when saving a file with Photoshop

We've been seeing a problem with several users that is hard to reproduce. Every once in a while when they try to save a file in Photoshop on the server they get a dialogue saying 'the file is locked, use Finder info to unlock the file'.
This file is located on the server and the problem only happens when doing a 'Save', not with a 'Save as'. The server is running 10.5.5 and the clients are 10.4.11. This is happening with Photoshop versions CS1, 2 and 3. It also happend with Illustrator CS3 once.
We've been experimenting with different scenario's using different ACL's and POSIX settings. Also, when the client reboots their machine the exact same 'Save' actions works again.

I've been receiving complaints about a similar issue over the past few weeks, except using Quark and Excel. I wonder if it's related to the 10.5.5 update. Are you sure you didn't get the version numbers reversed in your post? We're having the issue with 10.4.11 SERVER and 10.5.5. CLIENTS.
It's a file locking issue, so you probably won't fix it by changing the ACLs or POSIX permissions. The server thinks a different process still has the file open, so it's preventing you from changing the file. "Save As" works because it creates a new file.
You can probably eject & reconnect the volume from the client instead of fully rebooting.
The question is what's keeping the file open. You can run:
sudo lsof | grep <filename>
... in Terminal to see whether a given Mac has the file open. If the server comes back with a response to that command (don't worry what it says - you just want to see if anything comes back), then you know that the file is locked.
Next, go to each client that could have the file open and run the same command. If none of them have it open, you're probably looking at the same glitch that I've been. The server thinks a file is open but none of the clients do.

File sharing problems and horror story (nearly)

I use Leopard on a MacBook Pro, a MacBook and a iMac G4 800 MHz (unsupported model).
I have on the iMac and the MacBook Pro many users (the same ont he two machines) and I always use Fast User Switching.
I have had very few problems with Leopard until now; I like it even if there are some glitches or some new features which are not my cup of tea (hierarchical menus missing from the dock, stacks useless when there are many items, FireWall impossibilities (?) to open specific ports, Back to my Mac working on a Lan but not from outside until now, problems with a few apps (Parallels networking erratic), ...
Now about File Sharing.
Let say my main account is user1 (Administrator), and I have another user2 also administrator, plus user3, user4 standard users.
On the iMac I activate File Sharing.
On the MacBookPro, as user1, if I connect to the iMac Server (using afp://IPaddress_of_theiMac/) I do NOT get the dialog
"Enter your user name and password to access file server YYY
Connect to server as Guest or as Registered User"
but I directly get the dialog
"Select the volumes you want to mount on YYY"
From this, if I select user1 it mounts with full read/write permissions which is normal. It appears that I am connected with my Apple account user1&mac.com (same as mentionned in the Account panel of System Preferences).
On the other hand, if I try to connect to the user2 account, I only get limited access although in the File Sharing Preferences, user1/iMac is mentionned with full Read/Write preferences for the Home Folder of user2.
What is very surprising is that if I log on the MacBook Pro as user2, or user 3 or user4, then connect to the iMac, I first get the dialog to enter a user name and a password. This gives me access with the correct full permissions on user1/iMac or user2/iMac using the corresponding user name/password pair; this is the usual behaviour which is missing when trying to connect from user1/MacBook Pro.
Now for the Horror Story!
Trying to understand what was going on with the permissions of the user2/iMac account, I logged in to the iMac as user1, went to the Users folder and from there had a look on the informations about user2 home folder. In the lower part of the pannel, Sharing & Permissions says "You have no access" (which is normal) and this is followed by a table where users and permissions are listed. It seems user1 has Read and Write access in contradiction with the preceding phrase...
Anyway, I tried to modify these authorizations for user2 by clicking on the lock of the Information pannel and entering name and password of the administrator. Didn't go farther than that. By mistake, I hit Command-Delete and user2 was GONE from the list AND NOT ONLY from the list in the Information window! Using Fast User Switching and going to user2, nothing left on the Desktop and NO Home anymore.
In the System Preferences/Accounts panel, user2 was still mentionned.
In the Users folder, no user2 folder anymore.
Using once again Fast User Switching, I logged as user2 and got by magic an all new Home. Nothing left in Documents, Library or other user1 folders. Standard settings for icons, dock, etc.
My first move has been to use a very recent backup to restore everything (Thank you Mike Bombich from Copy Cloner!).
Once everything was back to normal, I had a look at the Trash from user1 and guess what, the Home folder of user2 was there, complete.
So now I am left with two questions
why is it I do not have the same dialogs when connecting from all the accounts although as far as I can see, configurations are the same?
why is it possible, from an Information pannel to delete the account of another user?
Thank you all for comments!

For the file sharing problems, answer is found in
http://docs.info.apple.com/article.html?artnum=306723

[Acrobat X Pro] File locks and page counts when printing

Hi,
We have two users on Acrobat X Pro Win 7 X32.
On both systems they have the following issues.
1) If they were to print only page 1 for example, they can set a page count of 5 copies and it would be fine. If later on they were to print page 10 and they would also like 5 copies, the page count has reverted to the default 1 copy. It doesn't remember the selection of 5 copies from the previous print.
Is this a bug?
2) File locks occur on all files even if they are specifically closed. The file lock is only removed once they close Acrobat down entirely. This has cause alot of problems. Has Adobe acknowledged this as a fault yet?
Thanks.

Make sure the Preview panel in Windows Explorer is disabled.

File Permission problems FCP and XSAN

We have 5 Mac Pros connected to our XSAN (2 Xserves and 2 Promise arrays.). When a file is created on one of the FCP Macs and saved on the XSAN, the permission are OK (Individual - R/W, Group - R/W & Everyone RO.)
The problem is when a file, generally audio (from our sound booth or music from an outside source) or a graphic (usually Photoshop from our Graphics folks) is brought in over the LAN and save to the XSAN volume, the permissions are Individual - R/W, no group is listed and Everyone - No Access.
If they try work on something that another user started, they get permission errors if the sequence contains a file that was brought in from the outside.
I know we can change permissions on a file, but there are so many of them that it is slowing down production.
Is there anything we can do to either eliminate this happening, or have something like a drop folder they can place a file in to automatically change the file permissions?
Any help with this would be greatly appreciated.
The MacPros are running OS X 10.5.8 and FCP 7.0.3 and the XSAN is running Mac OS X Server 10.5.8 and XSAN 2.2.
Thanks.

If files saved to the AFP reshare are inaccessible by the fibre clients try this in terminal on your AFP re-share...
sudo serveradmin settings afp:lock_manager = no
Then restart AFP (or reboot), and re-propagate permissions back to where you need them. This will hand off file locking duties from AFP to the Xsan, which will help keep your permissions correct.
JM
(Thanks to Shane for showing me this)

File Locking!!! Is this a BUG or there is something wrong in my code.

In new JDK v 1.4. new means of file locking are introuced, and it seems it is a little bit buggy yet (or maybe this one isn't a one). though it's better than nothing :)
here is 2 classes. first locks a file, the second attemts to change it.
import java.io.*;
import java.nio.*;
import java.nio.channels.*;
class FileLocker {
static File targetFile = new File ("D:\\Java",
                                     "manual.chm");
public static void main(String[] args)
      throws Exception
    RandomAccessFile fin = new RandomAccessFile (targetFile, "rw");
    FileChannel fChan = fin.getChannel();
    FileLock lock = fChan.lock();
    // to let other process to attempt to change the same file.
    Thread.currentThread().sleep(100000);
    lock.release();
    fChan.close();
    fin.close();
}and the other class
import java.io.*;
import java.nio.*;
import java.nio.channels.*;
class FileWriter {
static File targetFile = new File ("D:\\Java",
                                     "manual.chm");
public static void main(String[] args)
      throws Exception
    // this is better/more secure way to access files.
    RandomAccessFile f = new RandomAccessFile (targetFile, "rw");
    // next line deletes the file content even if file locked.
//    FileOutputStream f = new FileOutputStream (targetFile);
//--this parts is not needed as the problem is in first 2 lines
    FileChannel fChan = f.getChannel();
    if (fChan.isOpen()) {
      System.out.println("File is Opened, can't write");
    } else
      f.write(-1);
}so when i use FileInputStream for open stream to write,
constructor deletes the targetFile (makes it size equal to 0)
at once i create new FileInputStream object. Since, when i
use RandomAccessFile to open stream for writting nothing happens.
after that, f.write (-1); throws exception regardless the way the
uoutput stream was created.
So i think there is some problem in FileInputStream class' constructor.

OK, I know you mean FileOutputStream instead of FileInputStream in the above message. Looks to me like you've discovered a bug in the way Java is locking the file - locking the whole contents of a file (using the no-args lock or tryLock methods) doesn't prevent other programs, including Java, from overwriting some, if not all, of the file. Note that this occurs even on Windows 2000, where exclusive locks appear to be well supported.
I've found a similar problem where saving from Outlook appears to zero the whole of the locked file. Saving from other programs that are a little more careful, such as XEmacs, appears to only (!) truncate the file to 0, as the FileOutputStream does.
From what I can tell, in JDK 1.4.2 RandomAccessFiles respect each others' locks, but nothing else does.

ITunes Library File Locked

Hi,
Have been using iTunes 10.5 on my WinXP machine - no problems. During a movie download tonight, iTunes crashed. Tried to reopen and got the infamous error "iTunes Library file locked or on a locked disk..." Tried several remedies listed.
Verified that MyMusic folder and contents are not READ ONLY. I am unable to rename, edit, or move the file...she's locked up tight.
Tried repairing the Windows Registry assignment using the Tweak UI utility discussed in another thread. No joy.
Tried starting iTunes from another account on the PC - iTunes boots fine.
Pulling my hair out (what little is left)...Any ideas out there ???
HELP !

Fixed. For those using WinXP...Here's what I had to do:
It was a file properties thing as mentioned in other posts, but to change the file properties...
1. Boot Windows in SAFE MODE by holding F8 down during bootup
2. Log on as Administrator
3. Navigate to the iTunes Libary.itl file (My Music/iTunes)
4. Right Click and pull up the file properties
5. Under Security, re-add the user account to the file permissions
6. Then change file permissions to FULL (Read/Write/Edit...)
7. Reboot & Viola !
Once you unlock the write protected status (which got defaulted to the Adminstrator account), iTunes opens just fine.

Why is this file locked (man chflags), does it need to be, and is it safe to unlock it?

Why is this file locked (man chflags), does it need to be, and is it safe to unlock it?
~/Library/Application Support/Adobe/Enterprise/Resources/Resource_3_1.db
Type this into a terminal in OS X, the above file appears to have a flag set to lock.
x-man-page://chflags

<the-sound-of-crickets>
The reason I'm asking, we have a bunch of computers we inherited that have some permissions issues within each user's respective home directory ("~"). The issue effects Acrobat Pro X's ability to launch ("Internal error occurred") since it tries to get access files/folders it doesn't have access to when the user launches. Recursively setting ownership to the respective user fixes the problem (and follows Apple's guidelines). However, that one file appears to have the unix file lock set (man chflags). So we are using a pre-installation script on our push policy to loop through every home directory. It appears the above file is the only one that won't let us change permissions.
Don

File Locking in XI-

Hi all,
   I need to implement file locking technology for all of my interfcaes.Could anyone explain me the basics and detailed procdure for this?
Thanks
Rajesh

Hi Rajesh,
Look into the Note 821267 (3 question).
Unfortunately, the J2EE 1.3 technology the File Adapter is built upon does not support file locking. This limitation affects the File Adapter's operation. Depending on whether the JRE implementation for the operating system under which the adapter runs uses mandatory file locking or advisory file locking, opening a file that is currently being written to by another process will fail or not.
If opening the file fails, no problem exists and the adapter will try to open the file each poll interval until it succeeds.
However, if opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. Since XI 3.0 SP11 / PI 7.0 there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter
Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.
If this option is not available for the settings you would like to use, the following algorithm (to be implemented in your application) may be used to ensure that the File Adapter only processes completely written files:
-     Create the file using an extension, which does not get processed by the File Adapter, e.g., ".tmp"
-     Write the file content
-     Rename the file to its final name, so the File Adapter will notice its existence and pick it up
Source: SAP Note
Regards
San

File locks problem

Similar Messages

Maybe you are looking for