No. It is a Solaris 9 and older documented behavior.
If you kill and restart inetd, be aware that any environment variables in your shell are inherited by a shell for an incoming telnet session. For example, if you have USER=root in your environment, a user who connects to your machine with telnet inherits USER=root.
Quote:
Or should I have restarted the service some other way?
If your goal was for inetd to reread its configuration, the documented way would have been to send SIGHUP to the inetd process, eg:
Note that current Solaris releases (10, 11) no more use the same mechanism to restart this service so do not exhibit this issue.
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)
--------------------------------------------------------------------------------
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)
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)
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)
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)
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)
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 CENTOS
shell-quote
SHELL-QUOTE(1) User Contributed Perl Documentation SHELL-QUOTE(1)NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS --debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.16.3 2010-06-11 SHELL-QUOTE(1)