3 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi all
I would like to know how to run task2.service after task1.service has finished.
task1.service has a timer (task1.timer), that makes it run every 5 minutes
OnCalendar=*:0/5task2.service is basically a script, that has to work on the files created after task1 has finished.
This is what I... (2 Replies)
Discussion started by: guilliber
2 Replies
2. Solaris
Hi,
We are using solaris 10. One of the service was not allowed to start due to security check and violation.
Do you know what is the service is doing and what does the impact if it is disabled.
thanks,
Name of service:
/application/management/hwmgmtd (2 Replies)
Discussion started by: xitrum
2 Replies
3. HP-UX
Hi I'm wondering,
Is there a way to run an application as a background service on HP-UNIX? I'm a complete noobie! Basically I got an application that runs as an NT service on windows. This application is cross-platform and I am wondering if I could run it as some background service on HP-unix... (2 Replies)
Discussion started by: jun27
2 Replies
LEARN ABOUT DEBIAN
critical_enter
CRITICAL_ENTER(9) BSD Kernel Developer's Manual CRITICAL_ENTER(9)
NAME
critical_enter, critical_exit -- enter and exit a critical region
SYNOPSIS
#include <sys/param.h>
#include <sys/systm.h>
void
critical_enter(void);
void
critical_exit(void);
DESCRIPTION
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing
on a CPU will not be preempted. Specifically, a thread in a critical region will not migrate to another CPU while it is in a critical
region. The current CPU may still trigger faults and exceptions during a critical section; however, these faults are usually fatal.
The critical_enter() and critical_exit() functions manage a per-thread counter to handle nested critical sections. If a thread is made
runnable that would normally preempt the current thread while the current thread is in a critical section, then the preemption will be
deferred until the current thread exits the outermost critical section.
Note that these functions are not required to provide any inter-CPU synchronization, data protection, or memory ordering guarantees and thus
should not be used to protect shared data structures.
These functions should be used with care as an infinite loop within a critical region will deadlock the CPU. Also, they should not be inter-
locked with operations on mutexes, sx locks, semaphores, or other synchronization primitives. One exception to this is that spin mutexes
include a critical section, so in certain cases critical sections may be interlocked with spin mutexes.
HISTORY
These functions were introduced in FreeBSD 5.0.
BSD
October 5, 2005 BSD
