Sponsored Content
Operating Systems Solaris LUn' unmapped from storage still showing on Solaris 10 Post 302947040 by bentech4u on Monday 15th of June 2015 01:06:50 AM
Old 06-15-2015
this is related to process search

Code:
root@globalares2.example.com #ps -u 1002
ps: unknown user 1002
root@globalares2.example.com #ps -U 1002
ps: unknown user 1002
root@globalares2.example.com #more /etc/passwd | grep -i 1002

---------- Post updated 06-15-15 at 12:06 AM ---------- Previous update was 06-14-15 at 11:45 PM ----------

HI, i found the same server has 2 zones and 2 LUN from same storage is assigned to these 2 zones, and the userid 1002 is with one of the zone

Code:
root@test.example.com #zoneadm list | awk 'NR>1' | while read n ; do echo $n ;zlogin $n more /etc/passwd | grep -i 1002;done
uatfindbr
applfin:x:1002:111::/export/home/applfin:/bin/ksh
applshut:x:1002:111:backup-operation:/export/home/applshut:/bin/sh
applstart:x:1002:111:backup-operation:/export/home/applstart:/bin/sh

 

8 More Discussions You Might Find Interesting

1. Solaris

command to scan Enterprise storage Lun disk in Solaris

I just installed IBMsdd on Solaris diver along with the patches recommended. I also installed 2 - 2Gigs qlogic fiber cards & the corresponding pkges for the cards. What command can I use to scan this LUN disks from my Soalris servers. Solaris doen't seem to be seeing this disks presented on it.... (2 Replies)
Discussion started by: Remi
2 Replies

2. Solaris

Solaris 9 or 10 LUN Limitations

Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions? I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to. Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

3. Solaris

new attached lun in solaris 10

hi, what are the steps to detect and configure a new attached lun in Solaris 10. Is there any difference between cfgadm and luxadm command ? rgds, snjksh (5 Replies)
Discussion started by: snjksh
5 Replies

4. Solaris

How to get LUN WWN in Solaris?

How to get LUN WWN (i.e LUN mapped from a storage box say Symmetrix or clariion) in Solaris. fcinfo command does give the Target port wwn but what i'm looking for is the LUN WWN. Any help is appreciated. (2 Replies)
Discussion started by: Manish00712
2 Replies

5. Solaris

Solaris 10, adding new LUN from SAN storage

Hello to all, Actually, currently on my Solaris box, I've a LUN (5TB space) from a EMC storage which is working fine, and a partition with ZFS filesystem is created for that LUN. as further you'll see in the logs, the "c4t6006016053802E00E6A9196B6506E211d0s2" is the current configured LUN in the... (4 Replies)
Discussion started by: Anti_Evil
4 Replies

6. Solaris

Mpathadm showing no paths to 1 lun, others luns are fine

Hi, I've noticed that mpathadm states that one of our luns has no active paths: /dev/rdsk/c6t60000970000298700009533031324333d0s2 Total Path Count: 4 Operational Path Count: 4 /dev/rdsk/c6t60000970000298700009533031333037d0s2 ... (3 Replies)
Discussion started by: badoshi
3 Replies

7. Solaris

Luxadm display not showing a LUN as expected

Hi all, I have the following LUN which is showing OK with its two paths: DEVICE PROPERTIES for disk: /dev/rdsk/c23t500507630A3BC579d123s2 Vendor: IBM Product ID: 2107900 Revision: 3010 Serial Num: 75WB0114900 Unformatted capacity:... (13 Replies)
Discussion started by: ludiegu
13 Replies

8. Post Here to Contact Site Administrators and Moderators

AIX server do not detect LUN from HP storage

ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 Replies
LIBXO(3)						   BSD Library Functions Manual 						  LIBXO(3)

NAME
xo_emit -- emit formatted output based on format string and arguments LIBRARY
library ``libxo'' SYNOPSIS
#include <libxo/xo.h> LIBXO(3) BSD Library Functions Manual LIBXO(3) NAME
xo_open_list xo_open_list_h xo_open_list_hd xo_open_list_d xo_open_instance xo_open_instance_h xo_open_instance_hd xo_open_instance_d xo_close_instance xo_close_instance_h xo_close_instance_hd xo_close_instance_d xo_close_list xo_close_list_h xo_close_list_hd xo_close_list_d -- open and close lists and instances LIBRARY
library ``libxo'' SYNOPSIS
int xo_open_list_h(xo_handle_t *xop, const char *name); int xo_open_list(const char *name); int xo_open_list_hd(xo_handle_t *xop, const char *name); int xo_open_list_d(const char *name); int xo_open_instance_h(xo_handle_t *xop, const char *name); int xo_open_instance(const char *name); int xo_open_instance_hd(xo_handle_t *xop, const char *name); int xo_open_instance_d(const char *name); int xo_close_instance_h(xo_handle_t *xop, const char *name); int xo_close_instance(const char *name); int xo_close_instance_hd(xo_handle_t *xop); int xo_close_instance_d(void); int xo_close_list_h(xo_handle_t *xop, const char *name); int xo_close_list(const char *name); int xo_close_list_hd(xo_handle_t *xop); int xo_close_list_d(void); DESCRIPTION
Lists are sequences of instances of homogeneous data objects. Two distinct levels of calls are needed to represent them in our output styles. Calls must be made to open and close a list, and for each instance of data in that list, calls must be make to open and close that instance. The name given to all calls must be identical, and it is strongly suggested that the name be singular, not plural, as a matter of style and usage expectations. A list is a set of one or more instances that appear under the same parent. The instances contain details about a specific object. One can think of instances as objects or records. A call is needed to open and close the list, while a distinct call is needed to open and close each instance of the list: xo_open_list("item"); for (ip = list; ip->i_title; ip++) { xo_open_instance("item"); xo_emit("{L:Item} '{:name/%s}':0, ip->i_title); xo_close_instance("item"); } xo_close_list("item"); Getting the list and instance calls correct is critical to the proper generation of XML and JSON data. EXAMPLE: xo_open_list("user"); for (i = 0; i < num_users; i++) { xo_open_instance("user"); xo_emit("{k:name}:{:uid/%u}:{:gid/%u}:{:home}0, pw[i].pw_name, pw[i].pw_uid, pw[i].pw_gid, pw[i].pw_dir); xo_close_instance("user"); } xo_close_list("user"); TEXT: phil:1001:1001:/home/phil pallavi:1002:1002:/home/pallavi XML: <user> <name>phil</name> <uid>1001</uid> <gid>1001</gid> <home>/home/phil</home> </user> <user> <name>pallavi</name> <uid>1002</uid> <gid>1002</gid> <home>/home/pallavi</home> </user> JSON: user: [ { "name": "phil", "uid": 1001, "gid": 1001, "home": "/home/phil", }, { "name": "pallavi", "uid": 1002, "gid": 1002, "home": "/home/pallavi", } ] LEAF LISTS
In contrast to a list of instances, a "leaf list" is list of simple values. To emit a leaf list, call the xo_emit() function using the ""l"" modifier: for (ip = list; ip->i_title; ip++) { xo_emit("{Lwc:Item}{l:item}0, ip->i_title); } The name of the field must match the name of the leaf list. In JSON, leaf lists are rendered as arrays of values. In XML, they are rendered as multiple leaf elements. JSON: "item": "hammer", "nail" XML: <item>hammer</item> <item>nail</item> ADDITIONAL DOCUMENTATION
Complete documentation can be found on github: http://juniper.github.io/libxo/libxo-manual.html libxo lives on github as: https://github.com/Juniper/libxo The latest release of libxo is available at: https://github.com/Juniper/libxo/releases SEE ALSO
xo_emit(3) HISTORY
The libxo library was added in FreeBSD 11.0. AUTHOR
Phil Shafer BSD
December 4, 2014 BSD
All times are GMT -4. The time now is 05:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy