05-21-2008
nexttiem, never panic! Just ask anyone from your team or inform your team lead / manager. Not knowing something wont hurt your job...its your response that could impact your job. The faster yoru response/communication, the better it is!
There will always be new scenarios and issues in life as well as at work. So never panic rather choose a smart response.
Good luck
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Backup Exec Agent won't start....
Question: Has anyone had any previous experience working with Backup exec for Unix? I'm running SCO Openserver 5.0.5 and Backup Exec agent Version 5.01 Revision 5.032 Basically, these are the commands I'm issueing and here is the output.
# cd etc
# cd... (1 Reply)
Discussion started by: PatMcCoy
1 Replies
2. Solaris
Hi
Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies
3. UNIX for Dummies Questions & Answers
After I log ino the machine, a window pops up indicating that I should check that the HOSTNAME is the same in these three files
/etc//rc.configd/netconf
/etc/hosts
/var/adm/inetd.sec
How do I change the hostname in these files?
Thanks,
Mike h (1 Reply)
Discussion started by: hutchin
1 Replies
4. SuSE
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Discussion started by: dave521
5 Replies
5. Solaris
Hi.
I got this message in our sun station and it stuck
Setting default IPv4 interface for multicast: add net 224.0/4: gateway pecsun22
but i can still telenet the station...
who could i fix this..
appreciate your help (7 Replies)
Discussion started by: eykyn17
7 Replies
6. Red Hat
im running rh 9 on my vmware, i tryed changing the graphics card mode
to resize the desktop, after restarting i get a message X Server cannot start.
then it takes me to the consol screen to log on, "im new to using linux as of last night"
It would be helpfull if anyone can help me resolve... (4 Replies)
Discussion started by: aoteg
4 Replies
7. UNIX for Dummies Questions & Answers
on my AIX 6.1 CDE's ToolTalk server won't start. It says:
dtsession: Unable to exec /usr/dt/install/oldrules/dtrmrules.driver.
A file or directory in the path name does not exist.
How can I fix this? (0 Replies)
Discussion started by: rein
0 Replies
8. AIX
Hi,
My NFS does not work till I start HACMP. The NFS service is indeed started when server starts. But it is not in active state, when I use lssrc to check NFS services' status I find they are all in inoperative status. But after I start HACMP (smitty clstart), all NFS services become active... (4 Replies)
Discussion started by: qiulang
4 Replies
9. Red Hat
Hi, I am using redhat enterprise 5.7 have installed vsftpd successfully but every time I try to start the service it comes up with FAILED. Here is the contents of the vsftpd.conf file:
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=YES
#
#... (3 Replies)
Discussion started by: titley100
3 Replies
10. Fedora
Okay, I'm fairly green at Fedora, but it has worked like a gem until now. On startup I get a screen that says this:
Booting 'Fedora (3.6.11-4.fc16.x86_64)'
Loading Fedora (3.611-4.fc16.x86_64)
Loading initial ramdisk ....
_Fedora-16-x86_6: Unexpected inconsistency; run fsck manually.
... (6 Replies)
Discussion started by: Anchorsteamer
6 Replies
LEARN ABOUT DEBIAN
globus_gram_protocol_job_signal
GRAM
Signals(3) globus gram protocol GRAM Signals(3)
NAME
GRAM Signals -
Enumerations
enum globus_gram_protocol_job_signal_t { GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_CANCEL = 1, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_SUSPEND = 2,
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_RESUME = 3, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_PRIORITY = 4,
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST = 5, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_EXTEND = 6,
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_UPDATE = 7, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_SIZE = 8,
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STOP_MANAGER = 9, GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_END = 10 }
Detailed Description
Enumeration Type Documentation
enum globus_gram_protocol_job_signal_t
GRAM Signals.
Enumerator:
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_CANCEL
Cancel a job.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_SUSPEND
Suspend a job.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_RESUME
Resume a previously suspended job.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_PRIORITY
Change the priority of a job.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST
Signal the job manager to commence with a job submission if the job request was accompanied by the (two_state=yes) RSL attribute.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_EXTEND
Signal the job manager to wait an additional number of seconds (specified by an integer value string as the signal's argument)
before timing out a two-phase job commit.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_UPDATE
Signal the job manager to change the way it is currently handling standard output and/or standard error. The argument for this
signal is an RSL containing new stdout, stderr, stdout_position, stderr_position, or remote_io_url relations.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STDIO_SIZE
Signal the job manager to verify that streamed I/O has been completely received. The argument to this signal contains the number of
bytes of stdout and stderr received, separated by a space. The reply to this signal will be a SUCCESS message if these matched the
amount sent by the job manager. Otherwise, an error reply indicating GLOBUS_GRAM_PROTOCOL_ERROR_STDIO_SIZE is returned. If standard
output and standard error are merged, only one number should be sent as an argument to this signal. An argument of -1 for either
stream size indicates that the client is not interested in the size of that stream.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_STOP_MANAGER
Signal the job manager to stop managing the current job and terminate. The job continues to run as normal. The job manager will send
a state change callback with the job status being FAILED and the error GLOBUS_GRAM_PROTOCOL_ERROR_JM_STOPPED.
GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_END
Signal the job manager to clean up after the completion of the job if the job RSL contained the (two-phase = yes) relation.
Author
Generated automatically by Doxygen for globus gram protocol from the source code.
Version 11.3 Mon Apr 30 2012 GRAM Signals(3)