i have been in trouble please help me out
i have developed a message queue.it is a simple message queue program
after running it give error like NO SPACE LEFT ON DEVICE
what is this error
how could i solve this problem i am working on solaris9.2 (2 Replies)
hi friend i am facing problem in taking input from a file to the variable ..
read fname
if
then
cd $fname
pwd
ls > new_temp1
cat new_temp1
fi
terminal=`tty`
exec < $new_temp1
while read line
do
echo $line
done
exec < $terminal (2 Replies)
As a mind refresher, I was thinking to start a new thread for ONE LINERS....funny/weird or any technical one liners....
Let me start first......
=================================
#!/bin/ssh
#The Unix Guru's View of Sex
unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ;... (3 Replies)
Well, this was kinda fun and different:
You Want to Spend Time with Friends and Family a UNIX.com Cartoon Explainer
https://youtu.be/6jPDpuxI2OA
You want to spend time with friends and family.
But you are stuck on some problem...
Your Linux or Unix code is buggy and you don't know... (1 Reply)
Discussion started by: Neo
1 Replies
LEARN ABOUT DEBIAN
tapset::kprocess
TAPSET::KPROCESS(3stap)TAPSET::KPROCESS(3stap)NAME
tapset::kprocess - systemtap kernel process probe points
DESCRIPTION
This family of probe points is used to probe the kernel's process activities. It contains the following probe points:
kprocess.create
Fires whenever a new process is successfully created, either as a result of one of the fork syscall variants, or a new kernel
thread.
Arguments:
task
a handle to the newly created process
new_pid
pid of the newly created process
kprocess.start
Fires immediately before a new process begins execution.
Arguments:
N/A
kprocess.exec
Fires whenever a process attempts to exec to a new program
Arguments:
filename
the path to the new executable
kprocess.exec_complete
Fires at the completion of an exec call
Arguments:
errno
the error number resulting from the exec
success
a boolean indicating whether the exec was successful
kprocess.exit
Fires when a process terminates. This will always be followed by a kprocess.release, though the latter may be delayed if the process
waits in a zombie state.
Arguments:
code
the exit code of the process
kprocess.release
Fires when a process is released from the kernel. This always follows a kprocess.exit, though it may be delayed somewhat if the
process waits in a zombie state.
Arguments:
task
a task handle to the process being released
pid
pid of the process being released
SEE ALSO stap(1), stapprobes(3stap)Intel, IBMTAPSET::KPROCESS(3stap)