04-23-2009
I am closing this thread.
Both AIX and Linux are already supported on pSeries.
There is nothing more to understand.
9 More Discussions You Might Find Interesting
1. AIX
Hello Gurus,
i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX.
Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk?
i tried:
# extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies
2. SuSE
Hi.
I was wondering if there was a way to get the PVIDs from the disks on a SuSE Enterprise 9 box. I have 2 hdisks from a VIO setup that have specific PVIDs. I'd like to match those 2 disk to the disks within the Linux box. Any tips?
thanks. (0 Replies)
Discussion started by: Stephan
0 Replies
3. Shell Programming and Scripting
I am running into a small issue and not sure how to fix it or where to even look at this point. I have a shell script on a a box called bluezebra. On this box I have a very small shell script.
#!/bin/ksh
ssh bluemarron "/lcl/apps/Tivoli/netcool/omnibus/bin/TESTING/TEST.sh" &
This script... (0 Replies)
Discussion started by: LRoberts
0 Replies
4. AIX
Hi ,
I am planing to buy IBM pSeries Power5 9111-285 1,9 GHz but I am confused with few things. I would be happy if you could clear it up for me ?
1.Do I have to buy some license in order to create Lpars ?
2.Do I have to buy some license in order to use HMC , micro - partiocioning , VIOS... (4 Replies)
Discussion started by: phobus
4 Replies
5. AIX
As I know PowerVM supports these OS's AIX IBM I and LINUX
but is there any blade or other hardware that allows us to use all these OS's (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
6. AIX
Hello,
I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization.
So when booted , it goes into OPEN Firmware
I/O Hosting requires a hosting partition boot not permitted exit called
> ok
Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies
7. AIX
Hidey Ho Folks,
Looking to buy a pServer for playing around with the IBM side of things. Looked around for a bit and notice that there is a significant price gap for the used 570's (Single Units) vs the 520's and 550's that folks are selling. Curious what to watch out for in either case? And... (6 Replies)
Discussion started by: Devyn
6 Replies
8. UNIX for Beginners Questions & Answers
I have an old database that ran on UNIX/LINUX that was archived and stored years ago. We currently run on Windows and have no way to open/view this database or recover data. Does anyone have any experience or know how to recover? All I know is that it was a UniVerse IBM product.
Thanks! (2 Replies)
Discussion started by: Chantelle
2 Replies
9. AIX
Hi,
when I boot I get an E1DC error code. I've looked it up and it says that this error occurs during the firmware check. But the error is called "Dynamic Console Selection" .
1- Machine stopped at LCD led display = E1DC = CA00E1DC
E1DC Dynamic console selection. (maybe cable or keyboard)... (3 Replies)
Discussion started by: filosophizer
3 Replies
TKILL(2) Linux Programmer's Manual TKILL(2)
NAME
tkill, tgkill - send a signal to a thread
SYNOPSIS
int tkill(int tid, int sig);
int tgkill(int tgid, int tid, int sig);
Note: There are no glibc wrappers for these system calls; see NOTES.
DESCRIPTION
tgkill() sends the signal sig to the thread with the thread ID tid in the thread group tgid. (By contrast, kill(2) can be used to send a
signal only to a process (i.e., thread group) as a whole, and the signal will be delivered to an arbitrary thread within that process.)
tkill() is an obsolete predecessor to tgkill(). It allows only the target thread ID to be specified, which may result in the wrong thread
being signaled if a thread terminates and its thread ID is recycled. Avoid using this system call.
These are the raw system call interfaces, meant for internal thread library use.
RETURN VALUE
On success, zero is returned. On error, -1 is returned, and errno is set appropriately.
ERRORS
EINVAL An invalid thread ID, thread group ID, or signal was specified.
EPERM Permission denied. For the required permissions, see kill(2).
ESRCH No process with the specified thread ID (and thread group ID) exists.
EAGAIN The RLIMIT_SIGPENDING resource limit was reached and sig is a real-time signal.
EAGAIN Insufficient kernel memory was available and sig is a real-time signal.
VERSIONS
tkill() is supported since Linux 2.4.19 / 2.5.4. tgkill() was added in Linux 2.5.75.
CONFORMING TO
tkill() and tgkill() are Linux-specific and should not be used in programs that are intended to be portable.
NOTES
See the description of CLONE_THREAD in clone(2) for an explanation of thread groups.
Glibc does not provide wrappers for these system calls; call them using syscall(2).
SEE ALSO
clone(2), gettid(2), kill(2), rt_sigqueueinfo(2)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
Linux 2017-09-15 TKILL(2)