Sponsored Content
Top Forums Programming sem_wait, sem_post confusion? Post 302582789 by gabam on Sunday 18th of December 2011 08:42:41 AM
Old 12-18-2011
Thanks a ton buddy!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

'tr' confusion

Good day, everyone! Could anybody explain me the following situation. If I'm running similar script: Var="anna.kurnikova" Var2="Anna Kurn" echo $Var | tr -t "$Var" "$Var2" Why the output is : anna KurniKova instead of Anna Kurnikova? :confused: Thank you in advance for any... (2 Replies)
Discussion started by: Nafanja
2 Replies

2. Programming

C fork Confusion :-?

Hi, I was trying to learn forking in C in UNIX. Somehow i still haven't been able to get the concept well. I mean, i do understand that fork creates an exact replica of the parent (other than the fact that parent gets the process id of the child and child gets 0 when fork is called). This is the... (2 Replies)
Discussion started by: ralpheno
2 Replies

3. Solaris

Printer confusion

I have printer old about 5 year , but I can not determine which driver to use output of ls -al /usr/share/lib/terminfo/h -rw-r--r-- 1 root bin 961 Jan 22 2005 h1000 -rw-r--r-- 1 root bin 1002 Jan 22 2005 h1420 -rw-r--r-- 1 root bin 1009... (2 Replies)
Discussion started by: solaris_user
2 Replies

4. Cybersecurity

LDAP; confusion

Hello, I hope all is well. Two issues that I am grappling with. One: Is this a true statement: (AIX, LDAP configured), even if authentication is configured with LDAP, the system would still need to be authenticated against local (/etc/passwd); incase of network failure? Two: I can log... (0 Replies)
Discussion started by: rsheikh
0 Replies

5. Shell Programming and Scripting

conditional confusion

Hell Unix.com Community: I am working on a personal project using yad v0.12.4 (zenity fork) and have hit a wall on how to show a progress bar while my function is processing. I have been all over the ABS Guide, googled 21 Linux-specific sites that I revere. I even asked on the yad-common... (4 Replies)
Discussion started by: Habitual
4 Replies

6. Programming

Undefined: sem_init, sem_post, sem_wait

Hi friends, I am using semaphores in my program, but when I compile the program, it gives the following error $ gcc sem.c -o sem -lpthread Undefined first referenced symbol in file sem_init ... (1 Reply)
Discussion started by: gabam
1 Replies

7. Shell Programming and Scripting

Confusion with PS

Hello All, I have a problem in counting number of process getting run with my current script name.. Here it is ps -ef | grep $0 | grep -v grep This display just one line with the PID, PPID and other details when i print it in the script. But when I want to count the numbers in my... (11 Replies)
Discussion started by: sathyaonnuix
11 Replies

8. Homework & Coursework Questions

Semaphores sem_wait sem_post problem

hallo! if there are many processes running and I initialize the semaphore like this: my_sem = sem_open(SEM_NAME, O_CREAT | O_RDWR, S_IRUSR | S_IWUSR, 10); (the last argument is 10) and then i use sem_wait(my_sem); sleep(5); sem_post; Will 10 processes be able to access the... (1 Reply)
Discussion started by: whatevernever
1 Replies

9. UNIX for Dummies Questions & Answers

Confusion with the concept of wc -c and wc -m

Is wc -c and wc -m same ? Shellscript::cat file1 hello Shellscript::cat file1 | wc -c 6 Shellscript::cat file1 | wc -m 6 Shellscript::file file1 file1: ASCII text Shellscript::uname -a Linux was85host 2.6.27.45-0.1-vmi #1 SMP 2010-02-22 16:49:47 +0100 i686 i686 i386 GNU/LinuxAtleast... (5 Replies)
Discussion started by: shellscripting
5 Replies
wuzzah(1)							      Wuzzah?								 wuzzah(1)

NAME
wuzzah - keep an eye out for friends on a local system SYNOPSIS
wuzzah [OPTIONS...] DESCRIPTION
wuzzah is a program that just sits around and scans the utmpx entries to watch when your friends log in and out. By default upon invoca- tion, wuzzah looks for the file ${HOME}/.wuzzah, and loads the list of buddies contained therein (which are separated by newlines), and then sits and watches. If no file is found, and no other readable file is specified (see OPTIONS), wuzzah will attempt to just watch for whomever the current uid maps, and failing that will just quit. OPTIONS
-h, --help an informative usage summary, though nothing you don't see here... -a, --all-users watches for all users on the system, period. -c, --exec-cmd=CMD execute CMD upon a login. NOTE: this is done with a call to system(2), so you can do things like piping and whatever else you can do with sh -c -f, --buddy-file=FILE use FILE as buddyfile. naturally FILE must be readable, and consists of usernames, one to a line. optionally, these usernames can be followed by a colon, and then a wuzzah command-line to override wuzzah's behavior for this specific user. -F, --no-buddyfile tells wuzzah to not bother loading any config files. -i, --interval=NUM sleep NUM seconds between each polling -m, --message=STRING use STRING as a message template to greet logged-in buddies. See the section FORMATS for more information. -n, --no-newline don't end the messages with newlines (normally does by default) -o, --process-once scan the login records once, then exit -p, --process-current by default wuzzah doesn't message users who were already logged in when started up. this option overrides such behavior and mes- sages them anyways (only useful with the -w/-c options) -q, --silent don't message buddies when they log in (default). -s, --status-message=STRING use STRING as a template for displaying the status of people logging in and out. See FORMATS for more information. -u, --users=LIST adds every user in LIST (a space/comma/colon separated list of users) to the buddy list -v, --version the current version and copyright. -w, --write-buddies turns on messaging of buddies as they log in. NOTE: this can get quite annoying rather quickly. tune in soon for a less annoying solution FORMATS
message templates can be defined as normal character strings, interspersed with special format characters. format characters consist of a `%', followed by a character, which defines situation-specific data. The current list of these characters is as follows: a the alert character ('a') b the name of the buddy who has logged in/out d the date, currently in HH:MM:SS format h and H the remote hostname or IP address (respectively) of your buddy's login l the line in/out on which the buddy is logged (typically, something like /dev/pts/9 or /dev/ttyS0) m whether or not you have just messaged your buddy (really only useful for the -s option) n an embedded newline character o your buddy's online status ("logged on" or "logged off") u your own username, as can best be determined by the program. EXAMPLES
a simple invocation: username@machine$ wuzzah (13:45:39) foo logged in on :0 (not messaging). (13:45:39) bar logged in on pts/11 (not messaging). Message from username@machine on pts/11 at 14:00 ... (wuzzah) username says: "shoutout to my homie foo." EOF an example with a little more user customization: username@machine$ wuzzah --message="hey, %b, it's %u. nice to see you at %d!" and when foo logs in, foo will get a message like so: Message from username@machine on pts/11 at 14:00 ... hey, foo, it's username. nice to see you at (14:00:00)! EOF FILES
$HOME/.wuzzah the default file containing the list of users to watch BUGS
don't know of any, but reports (and patches too) are always welcome. feel free to send them to the author. AUTHOR
sean finney <seanius@seanius.net> sean finney Sun Nov 17 02:41:45 EST 2002 wuzzah(1)
All times are GMT -4. The time now is 10:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy