01-28-2002
Re: root user?
Quote:
Originally posted by Kelam_Magnus
Are you the "root" user when you are trying to Kill this process?
I see that your directory is /home/joeuser. Do an "id" to see if you are root.
If you aren't the Admin, get to root have your Unix Admin try to remove it.
Just a thought...
Yeah. I am root on the machine. It's my firewall/proxy/webserver/packet sniffer machine here at the house. I do some perl/c coding on it from time to time but that is about it.
It's strange that the `gzip -c` has hung the way it has. Sometime in March I am bringing up the 23 rack from the garage to my office and I will have to power down the machine at that point. I reckon it will not be a problem after that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I can kill running processes on my linux red hat system using ctrl-c but cannot do it from command line of another terminal using kill -2 pid. Although I can kill them from command line using kill -9 pid and other signals. I would like to do it using the kill -2 pid.
Thanks for your suggestions (6 Replies)
Discussion started by: bbhayana
6 Replies
2. Solaris
Dear All,
I have one doubt - when u use netstat -na | grep 8080 to know the status of 8080 ports.when it is listed someone is accessing the 8080 ports
like this
*.8080 *.* 0 0 64000 0 LISTEN
172.19.69.39.8080 172.19.50.20.1929 65535 ... (6 Replies)
Discussion started by: shanshine
6 Replies
3. Shell Programming and Scripting
Hi Friends,
I am new to this forum as well as new to shell scripting.
I have a problem here and i need someone to solve this.
Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument .
There is a... (1 Reply)
Discussion started by: Prince89
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
First, I am running a scipt.While the script is running I realize that I dont want the script to be run so I am killing the script externally.Before the process gets terminated or killed it should delete all the temporary files created by the script.How to do this?Can anyone help me?
... (3 Replies)
Discussion started by: arthi
3 Replies
5. Shell Programming and Scripting
Hi all,
I have been searching all day for a nice solution to this problem.
I have three scripts. A start script, a child script and a stop script.
Script A (scripta.sh)
Its Child Script B (scriptb.sh)
Script C (kill_process.sh $PID)
Script A correctly traps the kill command sent from... (6 Replies)
Discussion started by: mark007
6 Replies
6. Shell Programming and Scripting
Hi friends,
i m in big trouble....
i have one script which connects two server ...like below..
script1.sh
-------------------------------------
bash test.sh &
eval x=$@
export x=`echo $x`
#echo $x
#
ssh user@8.2.5.6 bash /mbbv/location/script.sh $x|sed '/Binary file/d'... (1 Reply)
Discussion started by: Shahul
1 Replies
7. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
8. UNIX for Advanced & Expert Users
UNIX Tutorial Five
% kill %jobnumber
Does that not work on a stopped process? I've tried to kill a stopped process and it is not working. Or do you need a certain type of shell for this to work? I don't see anything about this in my man pages. (3 Replies)
Discussion started by: cokedude
3 Replies
9. UNIX for Dummies Questions & Answers
I was just playing with the processes and suddenly a question striked my mind:
What will happen if we kill directly the shell process?? :rolleyes:
Do anyone know?
Will the system shutdown?
Or the system wont let it be killed? (5 Replies)
Discussion started by: paras.oriental
5 Replies
10. Shell Programming and Scripting
Hi ,
I have a list of application process id's.
Is there a way to kill all the process listed below using the script, except the once which are starting with " Genesis "
adm 1522 ABC_Process.tra
adm 1939 Genesis_Process.tra
adm 2729 Genesis_Archive.tra
adm 3259 xyz_Process.tra (5 Replies)
Discussion started by: murali1687
5 Replies
LEARN ABOUT X11R4
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)