Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

if a terminal emulation and a .profile are set up differently will they conflict

keith demingware
Occasional Advisor

if a terminal emulation and a .profile are set up differently will they conflict

I get the following message from a few cron processes that seem to be telling me that i have a terminal problem but i am not sure what the issue is.

I am running unix 11.11 on a hp9000 server
I seem to be just getting them when cron runs.

From root Fri Jun 22 08:02:23 EDT 2007
Received: (from root@localhost)
by rihpl.ri.ng.ds.army.mil (@(#)Sendmail version 8.13.3 - Revision 2.003
- 2006/04/25/8.8.6) id l5MC2NQC012971
for comp; Fri, 22 Jun 2007 08:02:23 -0400 (EDT)
Date: Fri, 22 Jun 2007 08:02:23 -0400 (EDT)
From: HP Server
Message-Id: <200706221202.l5MC2NQC012971@rihpl.ri.ng.ds.army.mil>
Subject: cron

process not attached to terminal
Usage: who [-rbtpludAasHTqRm] [am i] [utmp_like_file]

r run level
b boot time
t time changes
p processes other than getty or users
l login processes
u useful information
d dead processes
A accounting information
a all (rbtpludA options)
s short form of who (no time since last output or pid)
H print header
T status of tty (+ writable, - not writable, x exclusive open, ? hung)
q quick who
R print host name
process not attached to terminal
Usage: who [-rbtpludAasHTqRm] [am i] [utmp_like_file]

r run level
b boot time
t time changes
p processes other than getty or users
l login processes
u useful information
d dead processes
A accounting information
a all (rbtpludA options)
s short form of who (no time since last output or pid)
H print header
T status of tty (+ writable, - not writable, x exclusive open, ? hung)
q quick who
R print host name

just when you thought you had the answer
1 REPLY
Ben Dehner
Trusted Contributor

Re: if a terminal emulation and a .profile are set up differently will they conflict

It looks like there is a cron script that is executing the 'who -m' command. This option requires that the current stdin is associated with a terminal or pseudo-terminal and not re-directed file IO. This has nothing to do with terminal emulation, profiles, or TERM setting. When a command is executed via cron, there is no tty or pty terminal associated with the process.
Trust me, I know what I'm doing