05-11-2006
It is very difficult to pinpoint the problem without seeing your code, but I think it's getting stuck in an infinite loop... Anything else and it'd crash, not hang. You may be able to narrow it down by using a debugger with breakpoints, or just inserting print statements at critical places in the code.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to setup several accounts on a solaris system.
(passwd,shadow,group)
My question is :
How can I create a group which can access a machine, but only in certain directories? (4 Replies)
Discussion started by: SmartJuniorUnix
4 Replies
2. UNIX for Advanced & Expert Users
Hello,
i was searching around for good solution for managing many nameservers to add the records on the slave servers and update them and if possible some web-based manegment for non-experianced customers.
anyone has an idea where can i find such solution? (1 Reply)
Discussion started by: Bashar
1 Replies
3. UNIX for Advanced & Expert Users
Does anyone know something about this? I have no idea what it means and how to do it. but if anyone can give me and explanation and also point me to a website, i'd really appreciate it (5 Replies)
Discussion started by: TRUEST
5 Replies
4. Solaris
Hello.
I have got Solaris 10 8/07 on x86 installed successfully using CDs. While I had inserted 1st CD - I created 2 new filesystems also.
But now after entering into Solaris - How do I manipulate sizes or created/delete filesystems by going to terminal?
Thank you! (15 Replies)
Discussion started by: panchpan
15 Replies
5. What is on Your Mind?
Hi,
I recently found this article in computerworld and I think it is very true - at least in my company ... what do you guys think - is the author right? Is it ignorant management that makes us IT people seem to be anti-social and weird?
Please share your thoughts
Kind regards
zxmaus (5 Replies)
Discussion started by: zxmaus
5 Replies
6. Solaris
I installed Solaris 10 in an old Dell computer given to me. The filesystem is ZFS (Default).
The problem is that after logging in as root (first login) I wanted to add a user : n2jkw.
I added the user at /export/home/n2jkw
BTW, /export/home is where the 150G extra Hard Drive is mounted to.... (20 Replies)
Discussion started by: n2jkw
20 Replies
7. UNIX for Dummies Questions & Answers
Hi guys,
I need to use regular expressions in linux and I'm not quite experience in that field, maybe someone could give me some help with it.
Basically, I need to take a text like this.
A234321=http://www.google..... a normal URL
But, I need to take the string starting at... (0 Replies)
Discussion started by: ocramas
0 Replies
8. Programming
Hello.
I need to simulate a few serial links (doing a simulation of an application for a robot) and found socat which, at least with minicom, is working flawlessly.
I would really like to make pts static: ie same numbers between reboots, and automatic (not me opening terminals and leaving... (2 Replies)
Discussion started by: erupter
2 Replies
LEARN ABOUT DEBIAN
critical_exit
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