Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What programs access shared library file Post 302265741 by glev2005 on Monday 8th of December 2008 11:09:29 AM
Old 12-08-2008
What programs access shared library file

I was curious how to tell which programs are accessing a file (libobjc.A.dylib) in /usr/lib
This file seems to be the culprit in a bunch of Safari crashes, and I just wanted to know if and what other programs use it.

Also, I was curious what a good way to find out what files are being written to when I make a preference change in the GUI.. obviously some are just simple preference plist files that are named in a way that is easy to know what they do, but say I enable a different Ethernet controller, and I have no idea what system file is written to, is there a command I can use to see what file was most recently written to?

Thanks!
 

10 More Discussions You Might Find Interesting

1. AIX

How to debug a shared library(.so file) on AIX?

How to debug a shared library(.so file) on AIX? (1 Reply)
Discussion started by: AlbertGao
1 Replies

2. UNIX for Dummies Questions & Answers

access collision with shared file system

Hello ALL, In my system, there are 14 machines running the same version of Linux RHEL4. The 14 machines use a NFS file system, i.e., a shared file system. My question is that if the programs in individual machines can access a common file simutaneously. Or, they have to access the file... (1 Reply)
Discussion started by: cy163
1 Replies

3. Programming

Shared memory for shared library

I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability. Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies

4. Linux

how to backtrace a shared library file (.so)

I have a shared library file (.so) and I need to know some information 1. By which GCC version was this .so built? 2. Was this .so built in 32 bits mode or 64 bits mode Any command / tools to backtrace such kind of information? Thanks in advance! (2 Replies)
Discussion started by: princelinux
2 Replies

5. Shell Programming and Scripting

How to change a Makefile from building static library to shared library?

Hi: I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library) Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies

6. HP-UX

Problem in Shared library file .sl on 64bit HP-UX 11.11

We are facing issue with shared library file, we are getting difference in content for same shared file for chatr command :confused: , below are the detail about *.sl file, even we are also getting difference in size of both file. can you please tell me what will be the issue for same. is my new... (1 Reply)
Discussion started by: amodkavi
1 Replies

7. Programming

Shared Memory Between C Programs

I'm involved in a project with multiple teams which are developing C code for a Linux machine and we would like to have our program pass data to one of the other group's programs. The immediate idea is to have shared memory between the programs which would simply consist of variables whose size and... (2 Replies)
Discussion started by: cmcmanus3
2 Replies

8. Shell Programming and Scripting

Shared File system- lib access issue

I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes. When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error. fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies

9. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

10. AIX

Add shared members from library to same library in a different directory

I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message. add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
DEFAULTS(1)						    BSD General Commands Manual 					       DEFAULTS(1)

NAME
defaults -- access the Mac OS X user defaults system SYNOPSIS
defaults [-currentHost | -host hostname] read [domain [key]] defaults [-currentHost | -host hostname] read-type domain key defaults [-currentHost | -host hostname] write domain { 'plist' | key 'value' } defaults [-currentHost | -host hostname] rename domain old_key new_key defaults [-currentHost | -host hostname] delete [domain [key]] defaults [-currentHost | -host hostname] { domains | find word | help } DESCRIPTION
Defaults allows users to read, write, and delete Mac OS X user defaults from a command-line shell. Mac OS X applications and other programs use the defaults system to record user preferences and other information that must be maintained when the applications aren't running (such as default font for new documents, or the position of an Info panel). Much of this information is accessible through an application's Prefer- ences panel, but some of it isn't, such as the position of the Info panel. You can access this information with defaults Note: Since applications do access the defaults system while they're running, you shouldn't modify the defaults of a running application. If you change a default in a domain that belongs to a running application, the application won't see the change and might even overwrite the default. User defaults belong to domains, which typically correspond to individual applications. Each domain has a dictionary of keys and values rep- resenting its defaults; for example, "Default Font" = "Helvetica". Keys are always strings, but values can be complex data structures com- prising arrays, dictionaries, strings, and binary data. These data structures are stored as XML Property Lists. Though all applications, system services, and other programs have their own domains, they also share a domain named NSGlobalDomain. If a default isn't specified in the application's domain, but is specified in NSGlobalDomain, then the application uses the value in that domain. The commands are as follows: read Prints all of the user's defaults, for every domain, to standard output. read domain Prints all of the user's defaults for domain to standard output. read domain key Prints the value for the default of domain identified by key. read-type domain key Prints the plist type for the given domain identified by key. write domain key 'value' Writes value as the value for key in domain. value must be a property list, and must be enclosed in single quotes. For exam- ple: defaults write com.companyname.appname "Default Color" '(255, 0, 0)' sets the value for Default Color to an array containing the strings 255, 0, 0 (the red, green, and blue components). Note that the key is enclosed in quotation marks because it contains a space. write domain 'plist' Overwrites the defaults information in domain with that given as plist. plist must be a property list representation of a dic- tionary, and must be enclosed in single quotes. For example: defaults write com.companyname.appname '{ "Default Color" = (255, 0, 0); "Default Font" = Helvetica; }'; erases any previous defaults for com.companyname.appname and writes the values for the two names into the defaults system. delete domain Removes all default information for domain. delete domain key Removes the default named key from domain. domains Prints the names of all domains in the user's defaults system. find word Searches for word in the domain names, keys, and values of the user's defaults, and prints out a list of matches. help Prints a list of possible command formats. OPTIONS
Specifying domains: domain If no flag is specified, domain is a domain name of the form com.companyname.appname. Example: defaults read com.apple.TextEdit -app application The name of an application may be provided instead of a domain using the -app flag. Example: defaults read -app TextEdit filepath Domains may also be specified as a path to an arbitrary plist file, with or without the '.plist' extension. For example: defaults read ~/Library/Containers/com.apple.TextEdit/Data/Library/Preferences/com.apple.TextEdit.plist normally gives the same result as the two previous examples. In the following example: defaults write ~/Desktop/TestFile foo bar will write the key 'foo' with the value 'bar' into the plist file 'TestFile.plist' that is on the user's desktop. If the file does not exist, it will be created. If it does exist, the key-value pair will be added, overwriting the value of 'foo' if it already existed. WARNING: The defaults command will be changed in an upcoming major release to only operate on preferences domains. General plist manipulation utilities will be folded into a different command-line program. -g | -globalDomain | NSGlobalDomain Specify the global domain. '-g' and '-globalDomain' may be used as synonyms for NSGlobalDomain. Specifying value types for preference keys: If no type flag is provided, defaults will assume the value is a string. For best results, use one of the type flags, listed below. -string Allows the user to specify a string as the value for the given preference key. -data Allows the user to specify a bunch of raw data bytes as the value for the given preference key. The data must be provided in hexidecimal. -int[eger] Allows the user to specify an integer as the value for the given preference key. -float Allows the user to specify a floating point number as the value for the given preference key. -bool[ean] Allows the user to specify a boolean as the value for the given preference key. Value must be TRUE, FALSE, YES, or NO. -date Allows the user to specify a date as the value for the given preference key. -array Allows the user to specify an array as the value for the given preference key: defaults write somedomain preferenceKey -array element1 element2 element3 The specified array overwrites the value of the key if the key was present at the time of the write. If the key was not present, it is created with the new value. -array-add Allows the user to add new elements to the end of an array for a key which has an array as its value. Usage is the same as -array above. If the key was not present, it is created with the specified array as its value. -dict Allows the user to add a dictionary to the defaults database for a domain. Keys and values are specified in order: defaults write somedomain preferenceKey -dict key1 value1 key2 value2 The specified dictionary overwrites the value of the key if the key was present at the time of the write. If the key was not present, it is created with the new value. -dict-add Allows the user to add new key/value pairs to a dictionary for a key which has a dictionary as its value. Usage is the same as -dict above. If the key was not present, it is created with the specified dictionary as its value. Specifying a host for preferences: Operations on the defaults database normally apply to any host the user may log in on, but may be restricted to apply only to a specific host. If no host is provided, preferences operations will apply to any host the user may log in on. -currentHost Restricts preferences operations to the host the user is currently logged in on. -host hostname Restricts preferences operations to hostname. BUGS
Defaults can be structured in very complex ways, making it difficult for the user to enter them with this command. HISTORY
First appeared in NeXTStep. Mac OS X Nov 3, 2003 Mac OS X
All times are GMT -4. The time now is 08:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy