tmchild exec service failed erron = 2 Post: 97555

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with Mail command: exec failed. errno=2.

I am trying to send email using the "mail" command. I keep getting an "exec failed. errno=2." message. Here is one the commands I have tried: mail test@mycompany.com < test1.out Any ideas what may be causing this error msg?

2. Red Hat

vsftpd service failed to start

hi, i am using RHEL 5 and i am not able to on the vsftp i have tried to on the vsftp service using command service vsftpd start Starting vsftpd for vsftpd: i am posting the content of my /etc/xinetd.d/vsftpd file # description: The vsftpd FTP...

3. Red Hat

VSFTPD Service Failed to Start

Today I have installed VSFTPD but service is failing to start. We have been using standard FTP successful but need to introduce an FTPS option. I have run YUM install VSFTPD and everything appeared to load ok. (If I run rpm - qa | grep vsftpd I get vsftpd-2.0.5-16.el5_4.1 which I...

4. Shell Programming and Scripting

Script Variables Inquiry, Values Okay in Standalone Exec, No-Show in Cron Exec

I have the following bash script lines in a file named test.sh. #!/bin/bash # # Write Date to cron.log # echo "Begin SSI Load $(date +%d%b%y_%T)" # # Get the latest rates file for processing. # d=$(ls -tr /rms/data/ssi | grep -v "processed" | tail -n 1) filename=$d export filename...

5. Solaris

How to check FTP service failed in between on Solaris 10?

Hi Guys, I need to check why FTP service on Solaris 10 machine did not work in between. What does Jun-29 means here? Does it mean that it has been RUNNING/UP since Jun 29th ? -bash-3.2$ sudo /usr/bin/svcs |grep -i ftp legacy_run Jun_29 lrc:/etc/rc3_d/S90proftpd online ...

6. Red Hat

Snmpd service failed to start on Red Hat 6

Dear community, I got the following error when I try to start the snmpd service: # service snmpd start Starting snmpd: Log say: Could someone help please? Thank you Lucas ---------- Post updated at 08:07 AM ---------- Previous update was at 07:50 AM ---------- DAMN!!!!...

LEARN ABOUT XFREE86

xinetd.log

XINETD.LOG(5)							File Formats Manual						     XINETD.LOG(5)

NAME

       xinetd.log - xinetd service log format

DESCRIPTION

       A  service configuration may specify various degrees of logging when attempts are made to access the service. When logging for a service is
       enabled, xinetd will generate one-line log entries which have the following format (all entries have a timestamp as a prefix):

	      entry: service-id data

       The data depends on the entry.  Possible entry types include:

	      START	  generated when a server is started

	      EXIT	  generated when a server exits

	      FAIL	  generated when it is not possible to start a server

	      USERID	  generated if the USERID log option is used.

	      NOID	  generated if the USERID log option is used, and the IDONLY service flag is used, and the remote end  does  not  identify
			  who is trying to access the service.

       In the following, the information enclosed in brackets appears if the appropriate log option is used.

       A START entry has the format:

	      START: service-id [pid=%d] [from=%d.%d.%d.%d]

       An EXIT entry has the format:

	      EXIT: service-id [type=%d] [pid=%d] [duration=%d(sec)]

       type can be either status or signal.  The number is either the exit status or the signal that caused process termination.

       A FAIL entry has the format:

	      FAIL: service-id reason [from=%d.%d.%d.%d]

       Possible reasons are:

	      fork	     a certain number of consecutive fork attempts failed (this number is a configurable parameter)

	      time	     the time check failed

	      address	     the address check failed

	      service_limit  the allowed number of server instances for this service would be exceeded

	      process_limit  a limit on the number of forked processes was specified and it would be exceeded

       A DATA entry has the format:

	      DATA: service-id data

       The data logged depends on the service.

	      login	  remote_user=%s local_user=%s tty=%s

	      exec	  remote_user=%s verify=status command=%s
			  Possible status values:

			  ok	    the password was correct

			  failed    the password was incorrect

			  baduser   no such user

	      shell	  remote_user=%s local_user=%s command=%s

	      finger	  received string or EMPTY-LINE

       A USERID entry has the format:

	      USERID: service-id text

       The text is the response of the identification daemon at the remote end excluding the port numbers (which are included in the response).

       A NOID entry has the format:

	      NOID: service-id IP-address reason

SEE ALSO

       xinetd(1L), xinetd.conf(5)

								   28 April 1993						     XINETD.LOG(5)