Origin of Wall Street’s Plunge Is Still Unclear to Regulators

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Origin of Wall Street’s Plunge Is Still Unclear to Regulators
# 1  
Old 05-08-2010
Origin of Wall Street’s Plunge Is Still Unclear to Regulators

By GRAHAM BOWLEY NYTimes.com A day after a harrowing plunge in the stock market, federal regulators were still unable on Friday to answer the one question on every investor's mind: What caused that near panic on Wall Street? Through the day and into the evening, officials from the Securities and Exchange Commission and other federal agencies hunted [...]

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Programming

Isosurface and a 2D figure with the same scale and origin using mayavi

I am using mayavi to plot an iso surface from a 3D array s using the following piece of code: src = mlab.pipeline.scalar_field(s) fig=mlab.pipeline.iso_surface(src, color=(1.0,0.0,0.0), contours=, opacity=0.3) mlab.pipeline.iso_surface(src, color=(0.0,1.0,1.0),contours=, opacity=0.3) Then... (0 Replies)
Discussion started by: jaldo0805
0 Replies

2. Programming

Unclear pointer and array

Hello, The purpose of the program is to print a sub string from the prompt inputs. I do not understand why char pointer does not work but char array will for line 40 and Line 41. ./a.out thisisatest 0 8 substring = "thisisat"And my code is: #include <stdio.h> #include <stdlib.h> #include... (29 Replies)
Discussion started by: yifangt
29 Replies

3. Shell Programming and Scripting

best practises for scripting + a few unclear points

Hi guys, Besides the points bellow, what would best practices for scripting be ? 1) set the PATH 2) unset the current environment (set -u ?) 3) (re)set the IFS to default value - space (IFS="" <- is this correct ?) 4) check the return code for each action inside the script (cd, rsync,... (1 Reply)
Discussion started by: da1
1 Replies
Login or Register to Ask a Question
time_lock_es(3) 					     Library Functions Manual						   time_lock_es(3)

NAME
time_lock_es - Check time-of-day locking (Enhanced Security) LIBRARY
Security Library (libsecurity.so) SYNOPSIS
#include <sys/types.h> #include <sys/security.h> #include <prot.h> int time_lock_es ( struct es_passwd *prpwd ); PARAMETERS
Specifies a protected password entry structure. DESCRIPTION
The time_lock_es() function performs time-of-day lock checking for the current date and time against the time-of-day specification in the fd_tod string of the prpwd parameter. The function returns 1 if the time lock is on and 0 if there is no lock. The fd_tod specification is like that found in the UUCP Systems file. The specification is a comma-separated list of entries. If the cur- rent time matches an entry in the specification, the time lock is not on. The entries are scanned until a match is found. If no match can be found, the time lock is on. Each entry appears as follows: <day><start_time-end_time> The day is one of the following: Matches any day of the week. Matches Monday through Friday. Sunday Monday Tuesday Wednesday Thursday Friday Saturday The times are military time, for example, 9:15 am is 0915, 6:00 pm is 1800, and 12:42 am is 0042. When start_time is less than end_time, the range of times contains valid times in which to log in that day. When the times are equal or there is only one time (including no time at all), the entire day is valid. When start_time is later than end_time, times outside the range are valid. For instance, if start_time is 04:15 and end_time is 02:00, then any time that falls outside the range of 02:00 to 04:15 is a valid time. NOTES
Programs using this function must be compiled with -lsecurity. In order to quickstart a program, the program must be linked as follows: -lsecurity -ldb -laud -lm See the shared library discussion in the Programmer's Guide for more information about using the quickstarting feature. delim off time_lock_es(3)