Searched refs:identify (Results 1 – 25 of 69) sorted by path

123

/illumos-gate/usr/src/cmd/Adm/
H A D	mime.types	2 #Do not delete the above line. It is used to identify the file type.
/illumos-gate/usr/src/cmd/cmd-inet/sbin/dhcpagent/
H A D	README.v6	231 to identify a session. Because DHCPv6 uses link local addresses for
/illumos-gate/usr/src/cmd/fm/dicts/
H A D	AMD.po	105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 201 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 217 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 233 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 249 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… [all …]
H A D	DISK.po	43 …epair procedure to replace the affected disk.\nUse fmdump -v -u <EVENT_ID> to identify the disk.\n" 75 …epair procedure to replace the affected disk.\nUse fmdump -v -u <EVENT_ID> to identify the disk.\n" 123 …epair procedure to replace the affected drive.\nUse fmdump -V -u <EVENT_ID> to identify the drive."
H A D	FMD.po	114 msgstr "Use fmdump -v -u <EVENT-ID> to identify the repaired components." 130 msgstr "Use fmadm faulty to identify the repaired components, and any suspects that still need to b… 146 msgstr "Use fmdump -v -u <EVENT-ID> to identify the repaired components."
H A D	GMCA.po	41 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 57 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 73 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 89 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 105 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 121 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 137 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 153 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 169 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… 185 msgstr "Schedule a repair procedure to replace the affected CPU. Use 'fmadm faulty' to identify th… [all …]
H A D	INTEL.po	505 msgstr "reseat or replace dimms on channel. Use 'fmadm faulty' to identify the channel." 521 msgstr "reseat or replace dimm. Use 'fmadm faulty' to identify the dimm." 537 msgstr "reseat or replace dimm. Use 'fmadm faulty' to identify the dimm." 553 msgstr "reseat or replace dimm. Use 'fmadm faulty' to identify the dimm." 569 msgstr "reseat or replace dimm. Use 'fmadm faulty' to identify the dimms." 633 msgstr "Replace faulty dimm. Use 'fmadm faulty' to identify the dimm." 729 msgstr "Schedule a repair procedure to replace processor. Use 'fmadm faulty' to identify FRU." 745 msgstr "Schedule a repair procedure to replace processor. Use 'fmadm faulty' to identify FRU." 761 msgstr "Schedule a repair procedure to replace processor. Use 'fmadm faulty' to identify FRU." 777 msgstr "Replace faulty dimm. Use 'fmadm faulty' to identify the dimm." [all …]
H A D	PCI.po	41 msgstr "Ensure latest drivers and patches are installed. Use fmdump -v -u <EVENT_ID> to identify t… 57 …ocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 73 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s)or driver(s).\n\nCheck for… 89 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).\n\nSchedule a repair pro… 105 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s)or driver(s).\n\nCheck for… 121 msgstr "Use fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).\n\nSchedule a repair pro… 153 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 217 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 249 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 281 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… [all …]
H A D	PCIEX.po	41 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 57 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 121 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 137 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 153 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 169 …epair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or co… 313 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify th… 361 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 377 msgstr "Schedule a repair procedure to replace the affected device. Use fmadm faulty to identify t… 393 msgstr "Use 'fmadm faulty' to identify the device and then update the firmware to the latest versio… [all …]
H A D	STORAGE.po	89 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 105 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 121 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 137 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 153 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 169 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 185 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 201 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 217 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… 249 msgstr "Refer to the Maintenance page in the Sun ZFS Storage UI to identify the failed component. I… [all …]
H A D	SUNOS.po	89 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 137 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 153 …rocedure to replace the affected device. Use fmdump -v -u <EVENT_ID> to identify the device or con… 169 msgstr "Ensure latest drivers and patches are installed. Use fmdump -v -u <EVENT_ID> to identify th…
H A D	ZFS.po	122 …t will\nalways detect that these devices are missing, even if it cannot identify all of\nthe devic…
/illumos-gate/usr/src/cmd/fm/eversholt/files/common/
H A D	pciex.esc	904 * Can use source-id payload to identify where the message came from. 1103 * driver wasn't hardened we may be able to identify the leaf device (and 1108 * complex is sufficient to positively identify this case. 1191 * ereport to identify the originator of the request. The ptlp/mdpe ereports 1266 * can be done using the source-id payload in the ptlp ereport to identify the 1570 * will identify the device from the ca ereport. 1573 * can still identify the leaf device from the source-id payload of the nonfatal
/illumos-gate/usr/src/cmd/fm/eversholt/files/i386/i86pc/
H A D	gcpu_amd.esc	42 * syndrome and syndrome-type, and usually also a resource FMRI to identify
/illumos-gate/usr/src/cmd/fwflash/
H A D	Makefile.com	39 ROOTUSRLIBFWFLASHIDF= $(ROOTUSRLIBFWFLASH)/identify
/illumos-gate/usr/src/cmd/fwflash/plugins/
H A D	Makefile.targ	60 $(HERMON-MELLANOX_LIB):= DYNFLAGS += -R/usr/lib/fwflash/identify 61 $(HERMON-MELLANOX_LIB):= LDLIBS += -L. $(ROOT)/usr/lib/fwflash/identify/hermon.so
/illumos-gate/usr/src/cmd/infocmp/
H A D	mapfile-intf	42 # infocmp interposes on progname[], so identify this as an interposer.
/illumos-gate/usr/src/cmd/look/
H A D	words	11411 identify
/illumos-gate/usr/src/cmd/lp/lib/oam/
H A D	msg.source	510 …"You must identify which printer should\nhandle your request by naming it or a\nclass of printers … 585 "Give the -f or -S option to identify\nform or print wheel to mount." 633 …e options, the\n-v option to name the direct connect\nport or the -U to identify the dial-out\nmet… 824 …don't want the\ncurrent print wheel used, enter the\ncommand again, and identify the print\nwheel …
/illumos-gate/usr/src/cmd/lp/model/
H A D	netstandard	226 # identify them here. 274 # identify them here.
H A D	standard	377 # identify them here. 409 # identify them here. 419 # take a list (e.g. -o lopt='a b c'), identify
H A D	tsol_netstandard	260 # identify them here. 308 # identify them here.
H A D	tsol_netstandard_foomatic	264 # identify them here. 325 # identify them here.
H A D	tsol_standard	393 # identify them here. 425 # identify them here. 435 # take a list (e.g. -o lopt='a b c'), identify
H A D	tsol_standard_foomatic	409 # identify them here. 441 # identify them here. 451 # take a list (e.g. -o lopt='a b c'), identify

123

Last Index update Sat Apr 27 21:55:35 UTC 2024