6월, 11월은 TOP500 순위가 발표되는 달입니다.
때를 맞춰 HPC에 관련된 회사들은 신제품을 대거 출시하죠..
세미나에서 제품 발표도 하고,,
WCCS -> HPC Server 2008 -> HPC Server 2008 R2 의 출시 시기를 보면,,
6월, 11월에 맞춰져 있는 것도 이 때문입니다.

이번에도 어김없이,, HPC Server 2008 R2 Beta1을 출시했네요..
11월 초에 발표되었습니다.
내부적으로는 Version 3라고 부른다고 하네요..
Windows Compute Cluster Server 2003 = V1
Windows HPC Server 2008 = V2
Windows HPC Server 2008 R2 = V3

다운로드 받으려면 connect.microsoft.com 에 로그인할 수 있어야 하구요..
싸이트에 접속하면,, Excel 관련 패키지가 보입니다.
cnet news의 제목을 보면,,
"Microsoft testing Excel for supercomputers"
http://www.microsoft.com/presspass/press/2009/nov09/11-16SC09PR.mspx

V1에서 Excel 과 CCS를 연동하려면, UDF를 작성해야 하고,,
번거로움이 많았는데,, 이제는 어떻게 해결했다는 건지,, 궁금하네요..

설치해 봐야 하는데,, 요즘 너무 게을러 져서....

ssh와 sftp는 분명히 같은 포트(Port 22)를 사용하는데,,
ssh 는 정상적으로 접속이 되고,, sftp는 접속이 안된다??
정말 황당 사건입니다.

유사한 사례를 살펴보니,,
Shell Startup Scripts 에서 echo 에 의한 ouput이 있는 경우
이런 문제가 발생할 수 있다고 하네요..

문제가 발생하는 경우,,
1. ssh 접속했을 때 예전과 다른 문자가 찍히는지 확인
2. 문자가 찍힐 경우 아래와 같은 startup scripts 를 열어서,,
   echo 에 의한 출력이 있는지 확인해 보세요..

$HOME/.bashrc
$HOME/.profile
/etc/bashrc
등등

3. 출력되는 부분이 있을 경우,, 지워보세요..

'Linux' 카테고리의 다른 글

Linux Backup & Restore  (0) 2010.08.02
[UDA] OS 자동설치 툴  (0) 2010.08.02
[TIP] Shell Script  (0) 2009.07.01
Play Station 3 의 굴욕  (0) 2009.06.30
Fedora CORE 설치 중 hpet 메시지에서 멈출 때..  (1) 2009.06.25
Rocks 5.3에서 samba 서버를 사용할 경우
iptables Firewall 때문에,, 외부에서는 접속이 안됩니다.
아래와 같은 명령으로 samba 관련 포트를 열어야 사용할 수 있습니다.

/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto tcp --dport 137 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto tcp --dport 138 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto tcp --dport 139 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto tcp --dport 445 --jump ACCEPT

/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto udp --dport 137 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto udp --dport 138 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto udp --dport 139 --jump ACCEPT
/sbin/iptables --insert INPUT --source your.ip.networks.0/255.255.255.0  --in-interface eth1 --proto udp --dport 445 --jump ACCEPT

iptables -L
service iptables save

얼마전에 "웹진화론 2" 란 책을 추천 받아서 읽어 보았다.
작가(우메다 모치오)가 좌우명처럼 생각하는 말 중에 하나가,, 이 말이다.
직역하면,, "the Paranoid 만 살아남는다.."
the Paranoid 가 그럼 뭐냐??
사전적 의미는 편집병자 이다..
즉 정상적인 사람은 아니다..
뭔가에 집착하고, 지나치게 병적으로 의심하는 사람..
Intel 의 전 회장이자 현 상임고문인 앤드루 그로브가 한 말이다.
나도 그럴 수 있을까?
매사에 놀라운 완벽주의와 집요한 실행력을 가진 자만이 살아남을 수 있는 것일까??
나의 좌우명은 뭐지?


출처 : http://www.intel.com/pressroom/kits/bios/grove/paranoid.htm

Only the Paranoid Survive: Book Preface

Sooner or later, something fundamental in your business world will change.

I'm often credited with the motto, "Only the paranoid survive." I have no idea when I first said this, but the fact remains that, when it comes to business, I believe in the value of paranoia. Business success contains the seeds of its own destruction. The more successful you are, the more people want a chunk of your business and then another chunk and then another until there is nothing left. I believe that the prime responsibility of a manager is to guard constantly against other people's attacks and to inculcate this guardian attitude in the people under his or her management.

The things I tend to be paranoid about vary. I worry about products getting screwed up, and I worry about products getting introduced prematurely. I worry about factories not performing well, and I worry about having too many factories. I worry about hiring the right people, and I worry about morale slacking off.


And, of course, I worry about competitors. I worry about other people figuring out how to do what we do better or cheaper, and displacing us with our customers.

But these worries pale in comparison to how I feel about what I call strategic inflection points.

I'll describe what a strategic inflection point is a bit later in this book. For now, let me just say that a strategic inflection point is a time in the life of a business when its fundamentals are about to change. That change can mean an opportunity to rise to new heights. But it may just as likely signal the beginning of the end.

Strategic inflection points can be caused by technological change but they are more than technological change. They can be caused by competitors but they are more than just competition. They are full-scale changes in the way business is conducted, so that simply adopting new technology or fighting the competition as you used to may be insufficient. They build up force so insidiously that you may have a hard time even putting a finger on what has changed, yet you know that something has. Let's not mince words: A strategic inflection point can be deadly when unattended to. Companies that begin a decline as a result of its changes rarely recover their previous greatness.

But strategic inflection points do not always lead to disaster. When the way business is being conducted changes, it creates opportunities for players who are adept at operating in the new way. This can apply to newcomers or to incumbents, for whom a strategic inflection point may mean an opportunity for a new period of growth.

You can be the subject of a strategic inflection point but you can also be the cause of one. Intel, where I work, has been both. In the mid-eighties, the Japanese memory producers brought upon us an inflection point so overwhelming that it forced us out of memory chips and into the relatively new field of microprocessors. The microprocessor business that we have dedicated ourselves to has since gone on to cause the mother of all inflection points for other companies, bringing very difficult times to the classical mainframe computer industry. Having both been affected by strategic inflection points and having caused them, I can safely say that the former is tougher. I've grown up in a technological industry. Most of my experiences are rooted there. I think in terms of technological concepts and metaphors, and a lot of my examples in this book come from what I know. But strategic inflection points, while often brought about by the workings of technology, are not restricted to technological industries.

The fact that an automated teller machine could be built has changed banking. If interconnected inexpensive computers can be used in medical diagnosis and consulting, it may change medical care. The possibility that all entertainment content can be created, stored, transmitted and displayed in digital form may change the entire media industry. In short, strategic inflection points are about fundamental change in any business, technological or not.

We live in an age in which the pace of technological change is pulsating ever faster, causing waves that spread outward toward all industries. This increased rate of change will have an impact on you, no matter what you do for a living. It will bring new competition from new ways of doing things, from corners that you don't expect.

It doesn't matter where you live. Long distances used to be a moat that both insulated and isolated people from workers on the other side of the world. But every day, technology narrows that moat inch by inch. Every person in the world is on the verge of becoming both a coworker and a competitor to every one of us, much the same as our colleagues down the hall of the same office building are. Technological change is going to reach out and sooner or later change something fundamental in your business world.

Are such developments a constructive or a destructive force? In my view, they are both. And they are inevitable. In technology, whatever can be done will be done. We can't stop these changes. We can't hide from them. Instead, we must focus on getting ready for them. The lessons of dealing with strategic inflection points are similar whether you're dealing with a company or your own career. If you run a business, you must recognize that no amount of formal planning can anticipate such changes. Does that mean you shouldn't plan? Not at all. You need to plan the way a fire department plans: It cannot anticipate where the next fire will be, so it has to shape an energetic and efficient team that is capable of responding to the unanticipated as well as to any ordinary event. Understanding the nature of strategic inflection points and what to do about them will help you safeguard your company's well-being. It is your responsibility to guide your company out of harm's way and to place it in a position where it can prosper in the new order. Nobody else can do this but you. If you are an employee, sooner or later you will be affected by a strategic inflection point. Who knows what your job will look like after cataclysmic change sweeps through your industry and engulfs the company you work for? Who knows if your job will even exist and, frankly, who will care besides you?

Until very recently, if you went to work at an established company, you could assume that your job would last the rest of your working life. But when companies no longer have lifelong careers themselves, how can they provide one for their employees?

As these companies struggle to adapt, the methods of doing business that worked very well for them for decades are becoming history. Companies that have had generations of employees growing up under a no-layoff policy are now dumping 10,000 people onto the street at a crack. The sad news is, nobody owes you a career. Your career is literally your business. You own it as a sole proprietor. You have one employee: yourself. You are in competition with millions of similar businesses: millions of other employees all over the world. You need to accept ownership of your career, your skills and the timing of your moves. It is your responsibility to protect this personal business of yours from harm and to position it to benefit from the changes in the environment. Nobody else can do that for you.

Having been a manager at Intel for many years, I've made myself a student of strategic inflection points. Thinking about them has helped our business survive in an increasingly competitive environment. I'm an engineer and a manager, but I have always had an urge to teach, to share with others what I've figured out for myself. It is that same urge that makes me want to share the lessons I've learned.

This book is not a memoir. I am involved in managing a business and deal daily with customers and partners, and speculate constantly about the intentions of competitors. In writing this book, I sometimes draw on observations I have made through such interactions. But these encounters didn't take place with the notion that they would make it into any public arena. They were business discussions that served a purpose for both Intel and others' businesses, and I have to respect that. So please forgive me if some of these stories are camouflaged in generic descriptions and anonymity. It can't be helped.

What this book is about is the impact of changing rules. It's about finding your way through uncharted territories. Through examples and reflections on my and others' experiences, I hope to raise your awareness of what it's like to go through cataclysmic changes and to provide a framework in which to deal with them.

Copyright © 1996 by Andrew S. Grove. All rights reserved. 

'ETC' 카테고리의 다른 글

ATTO  (0) 2011.06.16
이 또한 지나가리라  (0) 2010.11.25
휴브리스(hubris), 과거의 작은 성공을 잊어라  (0) 2009.11.17
가을인데,, 책읽기에 빠져 보심이...  (0) 2009.09.15
Lenovo T61 Multibooting  (4) 2009.07.22
Rocks 5.2 + RHEL 5.3 (x86_64) 버전
SGE-v62u2_1-1

qrsh 를 실행하면 아래와 같이 에러가 발생합니다.

error: error: ending connection before all data received
error:
error reading job context from "qlogin_starter"

아래 내용을 근거로 Queue 설정에서 아래쪽 두줄을 삭제합니다.

rsh_command                  /usr/bin/ssh
rlogin_command               /usr/bin/ssh


[root@frontend ~]# qconf -sconf
#global:
execd_spool_dir              /opt/gridengine/default/spool
mailer                       /bin/mail
xterm                        /usr/bin/X11/xterm
load_sensor                  none
prolog                       none
epilog                       none
shell_start_mode             posix_compliant
login_shells                 sh,ksh,csh,tcsh
min_uid                      0
min_gid                      0
user_lists                   none
xuser_lists                  none
projects                     none
xprojects                    none
enforce_project              false
enforce_user                 auto
load_report_time             00:00:40
max_unheard                  00:05:00
reschedule_unknown           00:00:00
loglevel                     log_warning
administrator_mail           none
set_token_cmd                none
pag_cmd                      none
token_extend_time            none
shepherd_cmd                 none
qmaster_params               none
execd_params                 none
reporting_params             accounting=true reporting=true \
                             flush_time=00:00:15 joblog=true sharelog=00:00:00
finished_jobs                100
gid_range                    20000-20100
qlogin_command               builtin
qlogin_daemon                builtin
rlogin_command               builtin
rlogin_daemon                builtin
rsh_command                  builtin
rsh_daemon                   builtin
max_aj_instances             2000
max_aj_tasks                 75000
max_u_jobs                   0
max_jobs                     0
max_advance_reservations     0
auto_user_oticket            0
auto_user_fshare             0
auto_user_default_project    none
auto_user_delete_time        86400
delegated_file_staging       false
reprioritize                 0
jsv_url                      none
qrsh_command                 /usr/bin/ssh
rsh_command                  /usr/bin/ssh
rlogin_command               /usr/bin/ssh
jsv_allowed_mod              ac,h,i,e,o,j,M,N,p,w

[root@frontend ~]# qconf -mconf
#rsh_command                  /usr/bin/ssh   ## 삭제
#rlogin_command               /usr/bin/ssh   ## 삭제

얼마전에 "성공 경험의 자기 우상화" 라는 말을 들었습니다.
과거에 이런 방식으로 문제에 접근했을 때 모든 일이 잘 해결되었기 때문에,
현재 나에게 일어나는 문제에 대해서도 동일한 방식으로 접근한다??
너무도 당연한 논리이다..
그런데,, 이런 접근 방식이 모두 성공하지는 않을텐데... 걱정이다.
아래 독재자의 예 처럼...........

 

휴브리스(hubris), 과거의 작은 성공을 잊어라

2009-09-24

[한국경제신문 2009.2.10일자]

 

모든 성공은 최면이요 마약이다. 언제든 반복될 수 있고 어디서든 통할 것만 같다. 그러나 경쟁이 있는 사회에서 그런 일은 잘 안 생긴다.

과거의 성공은 사다리일 뿐이다. 올라오는데 쓴 도구는 더 높은 곳으로 올라가는 데는 쓸모가 없다. 성공이란 사다리를 걷어찰 수 있어야 진정한 CEO의 길에 들어설 수 있다.

회사에서 2월은 의욕이 넘치는 시절이다. 경영진에 막 합류한 신임 임원들의 '고양된' 사기가 곳곳에서 넘친다.

그러나 스포츠에서 쉽게 알 수 있듯 흥분만큼 위험한 것도 없다. 고수를 만나면 여지없이 깨지고,엔돌핀이 너무 높아져 부하들과 코드가 안 맞는다. 더군다나 최악의 경기 상황이 한동안 계속될 수밖에 없는 현실이어서 성과도 기대만큼 나타나지 않는다.

장차 위대한 CEO가 되려면 초임 임원 시절부터 침착해야 한다. 방향을 잘 잡고 있는지 항상 자문해야 한다. 고수의 세계에선 한번의 실수로 승부가 갈린다. 특히 조심해야 할 대목은 과거의 성공 경험을 고집하는 것이다. 부장 시절에 재미를 본 방법을 계속 써먹다간 '부장감'으로 격하되고,목숨이 끝날 수도 있다.

사실 초임 임원들에만 해당되는 것은 아니다. 모든 리더는 과거의 성공 경험을 자신의 밑천으로 안다. 그것이 경험이라고 생각한다.

그러나 이렇게 변화 빠른 시절에 과거의 성공은 그야말로 과거일 뿐이다. 쉽게 모방되고 비결이 알려지는 시대에는 한번 성공한 것이 오히려 독이 되기도 한다.

역사학자 토인비는 역사를 바꾸는데 성공한 창조적 소수가 그 성공으로 인해 교만해져서 남의 말에 귀를 막고 독단적으로 행동하다 판단력을 잃게 되는 것
휴브리스(hubris)라고 불렀다.

원래의 뜻인 오만,자만을 넘어 '성공 경험의 자기 우상화'라고 부를 수 있는 현상이다. 총칼로 권력을 잡은 군인이 계속 그 방식으로 철권통치를 하다 결국 쿠데타로 실각하는 것이 휴브리스의 대표적인 사례다.

달콤한 유혹을 뜻하는 '마시멜로'도 같은 맥락이다. 어린 아이에게 마시멜로를 주고 15분간 안 먹고 참으면 하나 더 주겠다는 스탠퍼드대의 실험에선 3분의 1의 아이들이 참지 못하고 먹어치웠다. 유혹을 견뎌낸 아이들이 결국 크게 성공을 거뒀다.

성공은 이미 과거다. 과거의 경험이 통하지 않는 시대엔 성공도 버려야 할 기억이다. 과거의 내 방식이 더 이상 통하지 않을 것이라고 믿을 때 더욱 비장해진다. 마시멜로의 유혹을 이겨내며 휴브리스에 얽매이지 않을 때라야 당신의 경영에도 날개가 달릴 것이다.

권영설 한경 아카데미 원장 yskwon@hankyung.com
한경 가치혁신연구소 value.hankyung.com

'ETC' 카테고리의 다른 글

ATTO  (0) 2011.06.16
이 또한 지나가리라  (0) 2010.11.25
Only the Paranoid Survive - Andrew S. Grove  (0) 2009.11.17
가을인데,, 책읽기에 빠져 보심이...  (0) 2009.09.15
Lenovo T61 Multibooting  (4) 2009.07.22

+ Recent posts