From: lovecreatesbeauty on 22 May 2010 22:09 hello, i want to get .so libraries linked with process. the pmap can report these information but the proc manual says pmap is one of the dangerous commands which stop process while inspecting. what's the alternative to pmap? i want to get these about processes: full pathname to the executable, .so libraries related to process. the starttime reported by ps lacks of year part, can i just concatenate the year number of the current date to it? do you see solaris machines run for years? what's the starttime reported by ps on it? does it have the year part? thank you for your time.
From: lovecreatesbeauty on 22 May 2010 22:17 On May 23, 10:09 am, lovecreatesbeauty <lovecreatesbea...(a)gmail.com> wrote: > hello, i want to get .so libraries linked with process. the pmap can > report these information but the proc manual says pmap is one of the > dangerous commands which stop process while inspecting. what's the > alternative to pmap? > > i want to get these about processes: full pathname to the > executable, .so libraries related to process. > ldd can do it but i need to get the full pathname to the exact executable which launches the specific process. which or whereis perhaps aren't the right choice. > the starttime reported by ps lacks of year part, can i just > concatenate the year number of the current date to it? do you see > solaris machines run for years? what's the starttime reported by ps on > it? does it have the year part? > > thank you for your time.
From: Ian Collins on 22 May 2010 22:40 On 05/23/10 02:17 PM, lovecreatesbeauty wrote: > On May 23, 10:09 am, lovecreatesbeauty<lovecreatesbea...(a)gmail.com> > wrote: >> hello, i want to get .so libraries linked with process. the pmap can >> report these information but the proc manual says pmap is one of the >> dangerous commands which stop process while inspecting. what's the >> alternative to pmap? >> >> i want to get these about processes: full pathname to the >> executable, .so libraries related to process. >> > > ldd can do it but i need to get the full pathname to the exact > executable which launches the specific process. which or whereis > perhaps aren't the right choice. ps -o comm -- Ian Collins
From: Chris Ridd on 23 May 2010 01:38 On 2010-05-23 03:17:44 +0100, lovecreatesbeauty said: > On May 23, 10:09�am, lovecreatesbeauty <lovecreatesbea...(a)gmail.com> > wrote: >> hello, i want to get .so libraries linked with process. the pmap can >> report these information but the proc manual says pmap is one of the >> dangerous commands which stop process while inspecting. what's the >> alternative to pmap? >> >> i want to get these about processes: full pathname to the >> executable, .so libraries related to process. >> > > ldd can do it but i need to get the full pathname to the exact > executable which launches the specific process. which or whereis > perhaps aren't the right choice. Also pldd can get you the actual shared objects in use by a running process, including ones that are loaded via dlopen(3C). The warning for pmap also applies to pldd. -- Chris
|
Pages: 1 Prev: Need help with file command in solaris. Next: Container queries |