by jc » Mon, 05 Oct 1998 04:00:00
by Dav » Tue, 06 Oct 1998 04:00:00
If you mean you erased the locate command, then it depends on what
distribution you are using ....
Dave
1. PROCESS:kerbd: could not be located + PROCESS:lpNet: could not be located
Who received already times a similar error message? What has to mean
you? Thanks in advance
Ticket created from SERVING event message
**************************************************
Object: O---L-
Application: /xx/xx
MessageGroup: xxx
Severity: Critical
CreationTime: 22.05.2000 18:08:10
Text:
*****
MSG-ID: 87 MSG-TEXT: SOURCE: SNMP ubsxxx.xx.SOLARIS_NUC.PROCESS_ERROR =>
PROCESS:kerbd: could not be located
MSG-NODE: svxxx
MSG-ID: 75 MSG-TEXT: SOURCE: SNMP ubsxx.HJ4.SOLARIS_NUC.PROCESS_ERROR =>
PROCESS:lpNet: could not be located
MSG-NODE: svpxxx
3. "find" and "locate" commands not working, linux RH5.2
5. pppd not work quoting "can't locate module"
6. Can I connect a third party HD to the internal SCSI in a 320?
7. "find" and "locate" commands not working, linux RH5.2
8. Locate and Xterm not working
9. Why is OpenBSD's locate update beating FreeBSD's locate update speed?
11. not tar 'ing files which are located in dir having whitespaces
12. Wiping old GRUB record not located in the MBR