07-19-2011
Threads are never really "solved" ... but an approach is often found.... there are always more than one solution; and so we do not mark them as "solved" and BTW, it is not a "pity" as you say, it is a forum "feature" because there is always more than one way to approach a problem in the UNIX and Linux environment.
If we thought it was so beneficial to mark threads "solved" we would have added this feature to the forums a long time ago. We do not see any great benefit for this and if other forums do it, then that is up to that site.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies
2. Linux
Dear Srs,
I'm getting this error on a Linux box, running Apache 2.0.52:
"host: isc_taskmgr_create: no available threads"
Making some search for those strings in Google, didn't tell me anything about this.. appears to be related to SELinux, but it's disabled in the box.
Any idea about... (0 Replies)
Discussion started by: Santi
0 Replies
3. Shell Programming and Scripting
Hi,
I have line in input file as below:
3G_CENTRAL;INDONESIA_(M)_TELKOMSEL;SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL
My expected output for line in the file must be :
"1-Radon1-cMOC_deg"|"LDIndex"|"3G_CENTRAL|INDONESIA_(M)_TELKOMSEL"|LAST|"SPECIAL_WORLD_GRP_7_FA_2_TELKOMSEL"
Can someone... (7 Replies)
Discussion started by: shis100
7 Replies
4. Programming
Hello all,
Is there any way that I can signal (wake) all threads that I have created without using pthread_cond_broadcast?
Cheers!
Aaron (6 Replies)
Discussion started by: mobility
6 Replies
5. What is on Your Mind?
We just added a new feature.
When tagging a thread, if you tag the thread "solved" the title of the thread will show up as blue (#0000FF) in various places (forum view, top stats, etc.)
So, if you want to show your thread as "solved" simply add a "solved" tag to the thread taglist.
... (16 Replies)
Discussion started by: Neo
16 Replies
6. UNIX for Dummies Questions & Answers
How to use "mailx" command to do e-mail reading the input file containing email address, where column 1 has name and column 2 containing “To” e-mail address
and column 3 contains “cc” e-mail address to include with same email.
Sample input file, email.txt
Below is an sample code where... (2 Replies)
Discussion started by: asjaiswal
2 Replies
7. Post Here to Contact Site Administrators and Moderators
Can the OP of a thread still mark the thread "Resolved" when the question is answered? (2 Replies)
Discussion started by: wbport
2 Replies
8. Shell Programming and Scripting
Hello.
System : opensuse leap 42.3
I have a bash script that build a text file.
I would like the last command doing :
print_cmd -o page-left=43 -o page-right=22 -o page-top=28 -o page-bottom=43 -o font=LatinModernMono12:regular:9 some_file.txt
where :
print_cmd ::= some printing... (1 Reply)
Discussion started by: jcdole
1 Replies
LEARN ABOUT DEBIAN
sigpause
SIGPAUSE(3) Linux Programmer's Manual SIGPAUSE(3)
NAME
sigpause - atomically release blocked signals and wait for interrupt
SYNOPSIS
#include <signal.h>
int sigpause(int sigmask); /* BSD */
int sigpause(int sig); /* System V / UNIX 95 */
DESCRIPTION
Don't use this function. Use sigsuspend(2) instead.
The function sigpause() is designed to wait for some signal. It changes the process's signal mask (set of blocked signals), and then waits
for a signal to arrive. Upon arrival of a signal, the original signal mask is restored.
RETURN VALUE
If sigpause() returns, it was interrupted by a signal and the return value is -1 with errno set to EINTR.
CONFORMING TO
The System V version of sigpause() is standardized in POSIX.1-2001.
NOTES
History
The classical BSD version of this function appeared in 4.2BSD. It sets the process's signal mask to sigmask. UNIX 95 standardized the
incompatible System V version of this function, which removes only the specified signal sig from the process's signal mask. The unfortu-
nate situation with two incompatible functions with the same name was solved by the sigsuspend(2) function, that takes a sigset_t * argu-
ment (instead of an int).
Linux Notes
On Linux, this routine is a system call only on the Sparc (sparc64) architecture.
Libc4 and libc5 only know about the BSD version.
Glibc uses the BSD version if the _BSD_SOURCE feature test macro is defined and none of _POSIX_SOURCE, _POSIX_C_SOURCE, _XOPEN_SOURCE,
_GNU_SOURCE, or _SVID_SOURCE is defined. Otherwise, the System V version is used.
SEE ALSO
kill(2), sigaction(2), sigprocmask(2), sigsuspend(2), sigblock(3), sigvec(3), feature_test_macros(7)
COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2010-09-12 SIGPAUSE(3)