Sponsored Content
Full Discussion: Rolling Back an Update
Operating Systems Linux Rolling Back an Update Post 302634359 by Brandon9000 on Thursday 3rd of May 2012 08:44:03 AM
Old 05-03-2012
Hi, Corona.

I also have to consider the possibility that the customer is trying it on basic, necessary software, so I would rather not uninstall and re-install in case something went wrong. They wouldn't like it if I wrecked the customer's system. I was hoping that someone had already worked out a system to do it, at least for some Linux family. I hate to concede defeat, but, at the same, time, I am probably not in a position to concoct a mammoth scheme for saving all necessary info on every update within my software. No one has ever solved this problem in a coherent way?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rolling back time

Hi all, Have a small problem. Back in October the pervious sys-admin (of a client's company) made the necessary adjustments to the system clock for daylight savings (Sydney time - +11 GMT). As far as I can gather, they just amended the time - NO TIMEZONE !?! Is there an effective and safe... (5 Replies)
Discussion started by: Cameron
5 Replies

2. AIX

back to back printing in UNIX

Hi , Can you suggest me how to back to back printing in UNIX? Is there any way? Kindly advise. Regards Vijaya Amirtha Raj (3 Replies)
Discussion started by: amirthraj_12
3 Replies

3. Shell Programming and Scripting

log rolling

Hi, I'm thinking of running a script via cron (every hour) to do the log rolling. The file is "file.txt" and there going to be 10 files rolling (file.txt.n). The file is being written constantly by an application. The script will do the following: 1. cat file.txt > file.txt.0 2. cat... (0 Replies)
Discussion started by: chaandana
0 Replies

4. IP Networking

Back-to-Back Connection using HBAs

Hi every body, Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber. Note it is direct connection & there is no switches between the servers. I'm concern about using HBA adapters, it is possible or not. Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies

5. AIX

rolling back Technology Level

Hi, is it possible to roll back currently updated Technology level ? what are steps required? Regards, Manoj (2 Replies)
Discussion started by: manoj.solaris
2 Replies

6. UNIX for Dummies Questions & Answers

Rolling back SQL transaction

Can some one help me related to .sql file issue. I have a .sqlfile and tried to read the file thru unix. In the .sqlfile I have error rows as well and when error comes I dont want to proceed further and need to roll back all the transactions. sample .sql file below insert into test... (2 Replies)
Discussion started by: sri_aue
2 Replies

7. UNIX for Dummies Questions & Answers

Middled Rolling average

Dear Help, The input file is below --- 13 2238422.00000 101083.00000 0.89024 0.00416 0.00467 14 2238318.00000 101090.00000 0.89100 0.00416 0.00467 15 2238209.00000 101100.00000 0.90964 0.00424 0.00466 16 2238104.00000 101104.00000 0.97568 0.00463 0.00475 17 2237991.00000 101113.00000... (8 Replies)
Discussion started by: Indra2011
8 Replies

8. What is on Your Mind?

SEO Update: Back On Page 1 for Google SERPs (between #6 and #8)

Well, good news... Just checked a number of browsers set to the US region of Google , NCR https://www.google.com/ncr unix.com was back on the first page, between #6 and #8. Will be interesting to see if we can make it back to our highest #4 ranking in 2019. Google Webmaster Tools... (4 Replies)
Discussion started by: Neo
4 Replies
sem_wait(3C)						   Standard C Library Functions 					      sem_wait(3C)

NAME
sem_wait, sem_trywait - acquire or wait for a semaphore SYNOPSIS
#include <semaphore.h> int sem_wait(sem_t *sem); int sem_trywait(sem_t *sem); DESCRIPTION
The sem_wait() function locks the semaphore referenced by sem by performing a semaphore lock operation on that semaphore. If the semaphore value is currently zero, then the calling thread will not return from the call to sem_wait() until it either locks the semaphore or the call is interrupted by a signal. The sem_trywait() function locks the semaphore referenced by sem only if the semaphore is currently not locked; that is, if the semaphore value is currently positive. Otherwise, it does not lock the semaphore. Upon successful return, the state of the semaphore is locked and remains locked until the sem_post(3C) function is executed and returns successfully. The sem_wait() function is interruptible by the delivery of a signal. RETURN VALUES
The sem_wait() and sem_trywait() functions return 0 if the calling process successfully performed the semaphore lock operation on the sem- aphore designated by sem. If the call was unsuccessful, the state of the semaphore is unchanged, and the function returns -1 and sets errno to indicate the error. ERRORS
The sem_wait() and sem_trywait() functions will fail if: EINVAL The sem function does not refer to a valid semaphore. ENOSYS The sem_wait() and sem_trywait() functions are not supported by the system. The sem_trywait() function will fail if: EAGAIN The semaphore was already locked, so it cannot be immediately locked by the sem_trywait() operation. The sem_wait() and sem_trywait() functions may fail if: EDEADLK A deadlock condition was detected; that is, two separate processes are waiting for an available resource to be released via a semaphore "held" by the other process. EINTR A signal interrupted this function. USAGE
Realtime applications may encounter priority inversion when using semaphores. The problem occurs when a high priority thread "locks" (that is, waits on) a semaphore that is about to be "unlocked" (that is, posted) by a low priority thread, but the low priority thread is pre- empted by a medium priority thread. This scenario leads to priority inversion; a high priority thread is blocked by lower priority threads for an unlimited period of time. During system design, realtime programmers must take into account the possibility of this kind of priority inversion. They can deal with it in a number of ways, such as by having critical sections that are guarded by semaphores execute at a high priority, so that a thread cannot be preempted while executing in its critical section. EXAMPLES
Example 1 The customer waiting-line in a bank may be analogous to the synchronization scheme of a semaphore utilizing sem_wait() and sem_trywait(): #include <errno.h> #define TELLERS 10 sem_t bank_line; /* semaphore */ int banking_hours(), deposit_withdrawal; void *customer(), do_business(), skip_banking_today(); thread_t tid; ... sem_init(&bank_line,TRUE,TELLERS); /* 10 tellers available */ while(banking_hours()) thr_create(NULL, NULL, customer, (void *)deposit_withdrawal, THREAD_NEW_LWP, &tid); ... void * customer(deposit_withdrawal) void *deposit_withdrawal; { int this_customer, in_a_hurry = 50; this_customer = rand() % 100; if (this_customer == in_a_hurry) { if (sem_trywait(&bank_line) != 0) if (errno == EAGAIN) { /* no teller available */ skip_banking_today(this_customer); return; } /*else go immediately to available teller & decrement bank_line*/ } else sem_wait(&bank_line); /* wait for next teller, then proceed, and decrement bank_line */ do_business((int *)deposit_withdrawal); sem_getvalue(&bank_line,&num_tellers); sem_post(&bank_line); /* increment bank_line; this_customer's teller is now available */ } ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ SEE ALSO
sem_post(3C), attributes(5), standards(5) SunOS 5.11 5 Feb 2008 sem_wait(3C)
All times are GMT -4. The time now is 07:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy