a user has had System Telnet up (for hours at a time) and been running various commands from the CUI menu.(its just client application) The following message appears over and over again in the account log:
2007/11/09! 03.56.29! E00549! Enq_pty! Tty.c! 119! PID (22597)! Operations ioctl (TCSETAW) failed,
file 'tty - errno 5: Input / output error
This problem is still happening. While the problem can be resolved, at least temporarily, by restarting all services.but I need to find out why this is occurring. The results vary slightly, but basically the client applications become unable to connect to the system.
In bash, you can do something like this:
#!/bin/bash
echo -n "What is your name? " > /dev/tty
read thename < /dev/tty
How can I do the same in python?
I have a python script that has the following content:
#!/usr/bin/python2.7
import getpass
import sys
import telnetlib
import... (2 Replies)
1. If I use an software application(which connects to the database in the server) in my local pc, how many PID should be registered? Would there be PID for the session and another PID for socket connection?
2. I noticed (through netstat) that when I logged in using the my software application,... (1 Reply)
question: for the below program
i just printed the value for pid, child pid and parent pid
why does it give me 6 values? i assume ppid is 28086
but can't figure out why there are 5 values printed instead of just two!
can someone comment on that!
#include<stdio.h>
#define DIM 8
int... (3 Replies)
msvc(8) System Manager's Manual msvc(8)NAME
msvc - control minit
SYNOPSIS
msvc [ -[uodpchaitko] ] [ -P pid ] service [...]
DESCRIPTION
msvc is the management interface to minit. service is the service directory name relative to /etc/minit. Starting with minit 0.9 you can
also include /etc/minit/ in the service name.
OPTIONS
If no option is given, msvc will just print a small diagnostic message to stdout, saying if the service is up, down or finished, which PID
it has if it is up, and for how long it has been in this state.
-u Up. If the service is not running, start it. If the service stops, restart it.
-o Once. If the service is not running, start it. If the service stops, do not restart it.
-d Down. If the service is running, send it a TERM signal and then a CONT signal. After it stops, do not restart it.
-p Pause. Send the service a STOP signal.
-c Continue. Send the service a CONT signal.
-h Hangup. Send the service a HUP signal.
-a Alarm. Send the service an ALRM signal.
-i Interrupt. Send the service an INT signal.
-t Terminate. Send the service a TERM signal.
-k Terminate. Send the service a KILL signal.
-P pid
Set PID. Tell minit the PID of the service is really pid. This is useful for services that fork themselves in the background but put
their real PID in a file, typically called /var/run/service.pid. Used by pidfilehack.
-D service
Print dependencies. This will print all the names of all the services that were started because this services depended on them.
Please note that this is not done recursively (i.e. if default depends on qmail and qmail depends on log, this will print qmail, not
qmail/log. But msvc -D qmail will print qmail/log).
-H Print history. This will print the names of the ten least recently spawned processes. This is useful if you see a process looping
(initialization fails and minit is restarting it all the time).
RETURN CODES
Generally, msvc return zero if everything is OK or 1 on error (could not open /lib/minit/in or /lib/minit/out or there is no process with
the given name). In diagnostic mode, it will exit 0 if the service is up, 2 if it is down or 3 if it is finished.
SEE ALSO pidfilehack(8), svc(8)msvc(8)