Job Schedular for Suse Enterprise SLES 11 SP2


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing Job Schedular for Suse Enterprise SLES 11 SP2
# 1  
Old 11-08-2013
Linux Job Schedular for Suse Enterprise SLES 11 SP2

We have a server with 160 hyper-threaded cpu's threads and 2Tb of RAM. I need to implement command line job queue and parallel thread usage for multiple user environment kindly suggest necessary tools to be installed.

I have understanding that sun grid engine like applications are available for clusters and not for single server, please correct me if i'm wrong.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Linux SuSE SLES 8 error..unable to issue shutdown command

the only way we can power off is if we actually press power button on server. Running on HP DL-G4. from root, when we issue command it just returns to root prompt. (1 Reply)
Discussion started by: amexboy
1 Replies

2. UNIX for Beginners Questions & Answers

Remote print from SLES (SAP) to AIX 7.1 04 sp2 virtual printer queue gets down

Hello Administrators. I have a bit difficult problem. I have local virtual printer that has backend defined in /etc/qconf to script which in turns sends the spool to the real device. whenever I print locally (from sap) the print works as it should. The printer queue after the print is done... (6 Replies)
Discussion started by: Deneth
6 Replies

3. Fedora

Install memcached on Suse 11 SP2

hi guys I am trying to install this extension for php named memcached but I am not really able to do it PECL :: Package :: memcached I have Suse 11 SP2 installed without any registration (I mean installed not paying subscription) so my question is there a way to install it like in... (0 Replies)
Discussion started by: karlochacon
0 Replies

4. SuSE

Failure of Vmware Server 2 installation on SLES 11 SP2

Issue: I am trying to install Vmware Server 2(VMware-server-2.0.2-203138.x86_64) installation on SUSE Linux Enterprise Server 11 (x86_64) SP2 and it fails with error: None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try... (3 Replies)
Discussion started by: rupeshkp728
3 Replies

5. UNIX for Dummies Questions & Answers

Suse 10 SP2 VNC Password

hi guys I've configured some CentOS where you can set a password for VNC and that password is requested before connecting to the normal user login But I found that Suse 10 SP3 has no such thing basically it has this configuration under /etc/xinetd.d/vnc service vnc1 { ... (2 Replies)
Discussion started by: kopper
2 Replies

6. SuSE

SLES 10 SP2 possible kernel problem, / slowly filling up

Hello Guys I first though about posting this to emergency but cause I fixed my issue with an reboot its not as important, more is important to me what caused this situation Some facts: OS: SLES 10 x64 SP2 (Virtualized Vmware ESX 3.5) / vmware tools status OK Soft: Oracle10g LVM... (1 Reply)
Discussion started by: kl1ngac1k
1 Replies

7. UNIX for Dummies Questions & Answers

Where are the repositories located in SUSE SLES 10 SP2

Hi, In SUSE SLES 10 SP2 where are the software repositories located? In CENTOS they are in /etc/yum.repositories or something like that. What does SLES use? (1 Reply)
Discussion started by: mojoman
1 Replies
Login or Register to Ask a Question
SGE_SHEPHERD(8) 				      Sun Grid Engine Administrative Commands					   SGE_SHEPHERD(8)

NAME
sge_shepherd - Sun Grid Engine single job controlling agent SYNOPSIS
sge_shepherd DESCRIPTION
sge_shepherd provides the parent process functionality for a single Sun Grid Engine job. The parent functionality is necessary on UNIX systems to retrieve resource usage information (see getrusage(2)) after a job has finished. In addition, the sge_shepherd forwards signals to the job, such as the signals for suspension, enabling, termination and the Sun Grid Engine checkpointing signal (see sge_ckpt(1) for details). The sge_shepherd receives information about the job to be started from the sge_execd(8). During the execution of the job it actually starts up to 5 child processes. First a prolog script is run if this feature is enabled by the prolog parameter in the cluster configura- tion. (See sge_conf(5).) Next a parallel environment startup procedure is run if the job is a parallel job. (See sge_pe(5) for more infor- mation.) After that, the job itself is run, followed by a parallel environment shutdown procedure for parallel jobs, and finally an epilog script if requested by the epilog parameter in the cluster configuration. The prolog and epilog scripts as well as the parallel environment startup and shutdown procedures are to be provided by the Sun Grid Engine administrator and are intended for site-specific actions to be taken before and after execution of the actual user job. After the job has finished and the epilog script is processed, sge_shepherd retrieves resource usage statistics about the job, places them in a job specific subdirectory of the sge_execd(8) spool directory for reporting through sge_execd(8) and finishes. sge_shepherd also places an exit status file in the spool directory. This exit status can be viewed with qacct -j JobId (see qacct(1)); it is not the exit status of sge_shepherd itself but of one of the methods executed by sge_shepherd. This exit status can have several mean- ings, depending on in which method an error occurred (if any). The possible methods are: prolog, parallel start, job, parallel stop, epi- log, suspend, restart, terminate, clean, migrate, and checkpoint. The following exit values are returned: 0 All methods: Operation was executed successfully. 99 Job script, prolog and epilog: When FORBID_RESCHEDULE is not set in the configuration (see sge_conf(5)), the job gets re-queued. Otherwise see "Other". 100 Job script, prolog and epilog: When FORBID_APPERROR is not set in the configuration (see sge_conf(5)), the job gets re-queued. Oth- erwise see "Other". Other Job script: This is the exit status of the job itself. No action is taken upon this exit status because the meaning of this exit status is not known. Prolog, epilog and parallel start: The queue is set to error state and the job is re-queued. Parallel stop: The queue is set to error state, but the job is not re-queued. It is assumed that the job itself ran successfully and only the clean up script failed. Suspend, restart, terminate, clean, and migrate: Always successful. Checkpoint: Success, except for kernel checkpointing: checkpoint was not successful, did not happen (but migration will happen by Sun Grid Engine). RESTRICTIONS
sge_shepherd should not be invoked manually, but only by sge_execd(8). FILES
sgepasswd contains a list of user names and their corresponding encrypted passwords. If available, the password file will be used by sge_shepherd. To change the contents of this file please use the sgepasswd command. It is not advised to change that file manu- ally. <execd_spool>/job_dir/<job_id> job specific directory SEE ALSO
sge_intro(1), sge_conf(5), sge_execd(8). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ SGE_SHEPHERD(8)