12-28-2018
Yes Ravinder, that is true.
I used to work hard on the computer and when my loved ones would come up to me and hug me and want to play and make me laugh, I would gently push them away; busy working on some IT project.
Now, unless it is an emergency (which is very rare), I stop all work and try to devote 100% of my attention to love, laughter, fun and embracing my loved ones in that moment when they come to me, even when I am busy focused on coding.
I could not agree with you more and writing these kind of "loved ones" ideas was going to be the "Part 2" of my thoughts for the end of 2018, in my future "thoughts for 2019" posts, but you kindly beat me to it.
Way to Go and Thanks!
This User Gave Thanks to Neo For This Post:
7 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Happy Thanksgiving holiday, everyone! Let's leave the computer alone, forget the Unix/Linux for a while, and enjoy your turkey and Foot~~~~~~~~~~~~~~~~~~~~~~ball~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (1 Reply)
Discussion started by: HOUSCOUS
1 Replies
2. Shell Programming and Scripting
hey all, I have set up a cron job which would be invoked at 1:00 am everyday. However, there is really no need to invoke such job if it's a public holiday so I am wondering if anyone have any idea on how to approach this? Thanks in advance! (2 Replies)
Discussion started by: mpang_
2 Replies
3. Shell Programming and Scripting
Hey all,
I have a question about cron job, I want to invoke a program to perform some operations
on database, however, this operation should only be invoked working day (weekday + not holiday)
. Scheduling a job on weekday is easy but how about holiday?
Thanks in advance! (1 Reply)
Discussion started by: mpang_
1 Replies
4. What is on Your Mind?
Hmm, didn't you press that "Submit new thread" button too early ? ;)
Reference this post:
https://www.unix.com/whats-your-mind/124692-seasons-greetings-happy-holidays-unix-linux-forums.html (15 Replies)
Discussion started by: jlliagre
15 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
I am new to autosys. Can anyone help me in writing autosys job for the below script?
Requirement is : 1.Every day it should run this script at particular time except on holidays.
2.The day after holiday some other script should be running.
Thanks in advance.
#!/bin/ksh
#set... (0 Replies)
Discussion started by: raghuramyenni
0 Replies
6. What is on Your Mind?
What is on Your Mind?
2018 FIFA World Cup - Wikipedia
I'm hoping that England are drawn into positions B2, D3, G3 or G4 so that all their games will be outside usual UK office hours and people will not desert the office with mystery illnesses to watch the games.
Expecting failure, so I... (1 Reply)
Discussion started by: rbatte1
1 Replies
7. What is on Your Mind?
/Me shakes my head.
I went to my old workplace on Wednesday last, 12-12-2018, and one of the passwords on a laptop used was amongst the 25 displayed.
Sadly I am unable to post the URL, garbage comes up...
I can't delete the post either...
--- Post updated at 08:34 PM ---
Try again... (6 Replies)
Discussion started by: wisecracker
6 Replies
LEARN ABOUT CENTOS
tevent_queue_tutorial
tevent_queue_tutorial(3) tevent tevent_queue_tutorial(3)
NAME
tevent_queue_tutorial - The tevent_queue tutorial
Introduction
A tevent_queue is used to queue up async requests that must be serialized. For example writing buffers into a socket must be serialized.
Writing a large lump of data into a socket can require multiple write(2) or send(2) system calls. If more than one async request is
outstanding to write large buffers into a socket, every request must individually be completed before the next one begins, even if multiple
syscalls are required.
To do this, every socket gets assigned a tevent_queue struct.
Creating a serialized async request follows the usual convention to return a tevent_req structure with an embedded state structure. To
serialize the work the requests is about to so, instead of directly starting or doing that work, tevent_queue_add must be called. When it
is time for the serialized async request to do its work, the trigger callback function tevent_queue_add was given is called. In the example
of writing to a socket, the trigger is called when the write request can begin accessing the socket.
How does this engine work behind the scenes? When the queue is empty, tevent_queue_add schedules an immediate call to the trigger callback.
The trigger callback starts its work, likely by starting other async subrequests. While these async subrequests are working, more requests
can accumulate in the queue by tevent_queue_add. While there is no function to explicitly trigger the next waiter in line, it still works:
When the active request in the queue is done, it will be destroyed by talloc_free. Talloc_free of an serialized async request that had been
added to a queue will trigger the next request in the queue via a talloc destructor attached to a child of the serialized request. This way
the queue will be kept busy when an async request finishes.
Example
* Metze: Please add a code example here.
*
Version 0.9.8 Tue Jun 17 2014 tevent_queue_tutorial(3)