06-04-2014
I moved this post ( Thread Hijacking is not tolerable...) to create a new thread here, but here you need to comply to the special rules so I am closing the thread and let you open a new one following the rules
Welcome by the way!
9 More Discussions You Might Find Interesting
1. Solaris
Hi all....I have a Sun Ultra2 that I want to use with my PC monitor. I have purchased an adapter that does not work and I was told I need to change my video card setting (if I can) to Separate Sync.....my Monitor product number ends in 1343......I am running SunOS 5.7 ......anyone have any ideas?
... (0 Replies)
Discussion started by: psantinello
0 Replies
2. Shell Programming and Scripting
I have a directory called UNIX 1 which contains 2 files and uploaded into two different servers. Now I want to check whether the directory contains both the files. If not, then need to sync the directory.
Please let me know how to do that in shell scripting. (2 Replies)
Discussion started by: madan1
2 Replies
3. UNIX for Dummies Questions & Answers
Hi everybody...
I want to sync files between unix client machine and windows 2003 server machine.
I thought of using Cygwin for windows server and then rsync between two to sync files, but have come to know that might be Cygwin will not be able to handle multiple clients request....
Can any... (2 Replies)
Discussion started by: lokeshsingla
2 Replies
4. Shell Programming and Scripting
Hello all. This may seem like a dumb/easy question but right now I have a little script I made that uses rsync to sync a directory that has files in it that may or may not be complete files. I want to come up with a better solution for this. What it is is I have a directory lets say /incomplete... (4 Replies)
Discussion started by: linuxn00b
4 Replies
5. Shell Programming and Scripting
Hi,
I developed one shell script where it will sync the files using perforce,
#!/bin/bash
TERM=linux
export TERM
clear
echo ""
$PATH
echo ""
cd /u/userk/p4/p4_client/TES_DATE
echo ""
echo "Sync p4 "
p4 sync
echo "Executing for second time "
p4 -u userk -p p4net:161 -c... (8 Replies)
Discussion started by: asak
8 Replies
6. News, Links, Events and Announcements
A new project was posted on your project board.
Project title: Bash Shell Tutoring
Estimated Budget:
$50/hr
Start date:
Immediately
Required skills:
Linux, Bash, Shell, UNIX
I work as a datawarehouse designer and developer.
Although I usually stick to the role of an analyst,... (0 Replies)
Discussion started by: Neo
0 Replies
7. Shell Programming and Scripting
Hi Linux Community
I would like to ask about how to compare files in deferent server with date.
Those A and B servers has the same folder, I have write a sample script to "ls" both folders and "diff" them, and then "rsync" the missing files.
It was running well, both A and B are sync, until... (2 Replies)
Discussion started by: lunaticdawn
2 Replies
8. Shell Programming and Scripting
Hi,
I would like to achieve below requirement,
I have a directory "/mydir" and I want to automatically sync/copy all the content of /mydir directory to "/yourdir" directory all the time.
meaning, if some application creates a file in /mydir, it supposed to be copied/available in "/yourdir"... (4 Replies)
Discussion started by: aaron8667
4 Replies
9. Shell Programming and Scripting
unzip -v gives CRC info of each file in a zip(in my case .EAR) file.
# unzip -v my-application.ear
Archive: my-application.ear
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
197981 Defl:N 183708 7%... (1 Reply)
Discussion started by: kchinnam
1 Replies
LEARN ABOUT XFREE86
pthread_self
PTHREAD_SELF(3) Linux Programmer's Manual PTHREAD_SELF(3)
NAME
pthread_self - obtain ID of the calling thread
SYNOPSIS
#include <pthread.h>
pthread_t pthread_self(void);
Compile and link with -pthread.
DESCRIPTION
The pthread_self() function returns the ID of the calling thread. This is the same value that is returned in *thread in the pthread_cre-
ate(3) call that created this thread.
RETURN VALUE
This function always succeeds, returning the calling thread's ID.
ERRORS
This function always succeeds.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+---------------+---------------+---------+
|Interface | Attribute | Value |
+---------------+---------------+---------+
|pthread_self() | Thread safety | MT-Safe |
+---------------+---------------+---------+
CONFORMING TO
POSIX.1-2001, POSIX.1-2008.
NOTES
POSIX.1 allows an implementation wide freedom in choosing the type used to represent a thread ID; for example, representation using either
an arithmetic type or a structure is permitted. Therefore, variables of type pthread_t can't portably be compared using the C equality
operator (==); use pthread_equal(3) instead.
Thread identifiers should be considered opaque: any attempt to use a thread ID other than in pthreads calls is nonportable and can lead to
unspecified results.
Thread IDs are guaranteed to be unique only within a process. A thread ID may be reused after a terminated thread has been joined, or a
detached thread has terminated.
The thread ID returned by pthread_self() is not the same thing as the kernel thread ID returned by a call to gettid(2).
SEE ALSO
pthread_create(3), pthread_equal(3), pthreads(7)
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 PTHREAD_SELF(3)