04-14-2011
You don't say what you want @ to do. But to make it stop killing the line, do stty kill undef
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I would like to connect UNIX server to UNIX server through shell scripts
and i have some concepts . But i am totally confused how to connect UNIX
server to UNIX server throuth running a script. It will be greatful to me if
any buddy will help me.
Thanks in advance.
Phatan:) (2 Replies)
Discussion started by: phatan
2 Replies
2. Shell Programming and Scripting
Hi,
I would like to connect UNIX server to UNIX server through shell scripts
and i have some concepts . But i am totally confused how to connect UNIX
server to UNIX server throuth running a script. It will be greatful to me if
any buddy will help me.
with simple example please.
Thanks in... (2 Replies)
Discussion started by: phatan
2 Replies
3. Solaris
Hi Guys,
I m using Solaris 10. When I run smc, I get message No SMC Server available please start the smc server in Server Toolbox Window. How can I start SMC (solaris management console) on solaris 10?
it's standalone server. (2 Replies)
Discussion started by: daya.pandit
2 Replies
4. UNIX for Dummies Questions & Answers
I am getting the fallowing error when i am trying to execute the scp commomd in shell script
warning: You have no controlling tty. Cannot read confirmation.
warning: Authentication failed.
Disconnected; key exchange or algorithm negotiation failed (Key exchange failed.).
scp2: warning: ssh2... (1 Reply)
Discussion started by: manit
1 Replies
5. Shell Programming and Scripting
Hi Gurus,
I'm a unix newbie and I would like to connect to multiple unix servers from unix server using shell script i.e from server a to server b,c,d etc. I want to copy the files from unix server a to server b, c, d. I can access staright using ssh without the need to have password and user... (5 Replies)
Discussion started by: sexyTrojan
5 Replies
6. HP-UX
When we ssh -i private key user@ip we get the password prompt. The sending servers public key is in the receiving server. We have blown away the known_hosts file on the sending server and restarted the ssh connection. We don't know what else to do. Any other suggestions? (15 Replies)
Discussion started by: jastanle84
15 Replies
7. Shell Programming and Scripting
Hi All,
Let me know how can i find and delete files from one unix server to another unix server which are 'N' days older.
Please note that I need to delete files on remote unix server.So, probably i will need to use sftp, but question is how can i identify files and folders which are 'N'... (2 Replies)
Discussion started by: sachinkl
2 Replies
8. Shell Programming and Scripting
hi,
Im using the following code for FTP
#!/usr/bin/ksh
ftp -v -n "10.29.45.11" << cmd
user "mahesva" "mahesva123"
get rtl.tar
quit
cmd
Below is the log when i run the above code
**********************************
Connected to 10.29.45.11.
220 (vsFTPd 2.0.1)
530 Please login with USER... (20 Replies)
Discussion started by: dll_fpga
20 Replies
9. Shell Programming and Scripting
Hi,
I have two unix servers i need to move files from one server to another.
For example:
i have some files in Server1 and i want to run script in server2 to move files from server1.
Any suggestion
Thanks in advance (1 Reply)
Discussion started by: karingulanagara
1 Replies
10. Ubuntu
Hello.
Doing my first steps in Linux and while trying to configure a DHCP server in Linux i encountered some problems:
TOPOLOGY:
- Laptop with Windows 8.1
- VM Player 12 with Linux installed (Ubuntu Server 14.04)
- ICS-DHCP-SERVER installed and running
- Another LAPTOP conected to a... (1 Reply)
Discussion started by: Portuguevos
1 Replies
LEARN ABOUT SUNOS
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Process killing procedure configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap, scope.scope
DESCRIPTION
Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit type.
The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.
If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop (for services: after the
stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to mixed,
the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
processes of the unit's control group. If set to none, no process is killed. In this case, only the stop command will be executed on
unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control
group continues to exist after stop unless it is empty.
Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
for more information.
Defaults to control-group.
KillSignal=
Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.
Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
tasks can be terminated cleanly.
SendSIGHUP=
Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".
SendSIGKILL=
Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
SEE ALSO
systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7), kill(2), signal(7)
systemd 237 SYSTEMD.KILL(5)