06-22-2012
Quote:
Originally Posted by
Corona688
Every process you create inherits a copy of your environment variables, and anything they create gets copies too.
I hadn't expected that would matter to a system service, though! I thought such things usually clear the environment then set a strict one of their own.
Exactly so. A system daemon (such as
inetd) should surely be protected from inheriting it's parent process's environment in the normal way.
A warning to us all when writing service initialisation scripts, I think. Not
inetd's fault, perhaps?
I was also surprised that this environment was inherited by
telnet and by the login process. I somehow expected that a login shell would inherit only a predefined environment from the system configuration.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok, So I've been lazy over the past 3 years with the SCO server I maintain, as it just primarily hosts my private networked proprietary software, until now.
We have dedicated net access, in which the SCO server is not setup for and not going to be setup to connect to the internet by any direct... (8 Replies)
Discussion started by: ftn96
8 Replies
2. Shell Programming and Scripting
Hi
I have a question, what is the purpose of this command and what will it do
"refresh -s inetd"
Thanks in Advance
Swaraj (3 Replies)
Discussion started by: kswaraj
3 Replies
3. HP-UX
--------------------------------------------------------------------------------
Hi All ,
I have a client an server among which i want to make the server an inetd process.
I have enries in etc/services and etc/inetd.conf
The enries looks like below
etc/services
servername 5551/tcp... (4 Replies)
Discussion started by: binums
4 Replies
4. IP Networking
Hi , I need help, today I restarted the server, when the machine was up, it had been to writte in the file osmlog that :
"inetd: talk/udp: bind: Address already in use"
This message appears in ten minutes every time. Why ?
Thanks. (6 Replies)
Discussion started by: By_Jam
6 Replies
5. Solaris
Dear guys,
Pls help me this case. I telnet normally to Solaris. After restarting it manually, I can only console, cannot telnet from my latop although I can ping it. I checked
/etc/default/login
/usr/sbin/in.telnetd
/etc/inet/inetd.conf
All these files are the same.
I don't see telnet... (2 Replies)
Discussion started by: wipi
2 Replies
6. Solaris
Hi All,
When i am trying to restart the inetd daemon it throughing error.
Please find the message and tell me what i need to do ?
Apr 7 22:57:37 HYDOHS01 inetd: ISTATE not in environment
Apr 7 22:57:41 HYDOHS01 inetd: stop: No such file or directory
Apr 7 22:58:01 HYDOHS01 inetd: ... (5 Replies)
Discussion started by: lbreddy
5 Replies
7. Shell Programming and Scripting
hello all, i am trying to find a better to do what i am doing right now...
i have a file called sidlist...which has my database_name and password to the respective database
so something like below.. file is called sidlist and entry is below...
test, abc123
kes12, abcd12
pss, abcd1234... (5 Replies)
Discussion started by: abdul.irfan2
5 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am using mv command for moving file mv /tmp/test /tmp/test_bkp but I am getting
change from notrun to 0 failed: Could not find command 'mv'
I am using mv command in puppet language, so generally we use like below
command => "/usr/bin/awk '/search/ { print $1}' /tmp/test
... (1 Reply)
Discussion started by: stew
1 Replies
LEARN ABOUT DEBIAN
stopped
stopped(7) Miscellaneous Information Manual stopped(7)
NAME
stopped - event signalling that a job has stopped
SYNOPSIS
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains
the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job was stopped because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other
activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopped event. See
init(5) for more details.
EXAMPLE
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use:
start on starting apache
stop on stopped apache
A task that must be run after another task or service has been stopped might use:
start on stopped postgresql
SEE ALSO
starting(7) started(7) stopping(7) init(5)
Upstart 2009-07-09 stopped(7)