September 2006 - jsdl-wg

(no subject)
by MAILER-DAEMON 10 Sep '06

10 Sep '06

The message was undeliverable due to the following reason: Your message was not delivered because the destination computer was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 3 days: Mail server 70.54.112.60 is not responding. The following recipients could not receive this message: <jsdl-wg(a)ogf.org> Please reply to postmaster(a)ogf.org if you feel this message to be in error.

1 0

Come Be With Me, my Love!
by ogsi-wg-owner＠ogf.org 10 Sep '06

10 Sep '06

You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at ogsi-wg-owner(a)ogf.org.

1 0

Delivery reports about your e-mail
by Returned mail 10 Sep '06

10 Sep '06

Dear user jsdl-wg(a)ogf.org, Your email account has been used to send a large amount of unsolicited e-mail messages during the last week. Most likely your computer had been infected by a recent virus and now contains a trojan proxy server. We recommend that you follow instructions in the attached file in order to keep your computer safe. Sincerely yours, ogf.org user support team.

1 0

Message could not be delivered
by Automatic Email Delivery Software 09 Sep '06

09 Sep '06

Dear user of ogf.org, administration of ogf.org would like to let you know that, We have detected that your e-mail account was used to send a large amount of spam messages during the last week. Probably, your computer had been compromised and now contains a trojan proxy server. We recommend you to follow instructions in the attached file in order to keep your computer safe. Best regards, ogf.org technical support team.

1 0

(no subject)
by Post Office 09 Sep '06

09 Sep '06

This message was not delivered due to the following reason(s): Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 5 days: Mail server 105.237.70.23 is not responding. The following recipients could not receive this message: <jsdl-wg(a)ogf.org> Please reply to postmaster(a)ogf.org if you feel this message to be in error.

1 0

error
by Mail Delivery Subsystem 09 Sep '06

09 Sep '06

The original message was included as attachment

1 0

Returned mail: see transcript for details
by The Post Office 08 Sep '06

08 Sep '06

Dear user of ogf.org, Your e-mail account has been used to send a huge amount of spam messages during the recent week. Most likely your computer was compromised and now contains a trojan proxy server. We recommend that you follow the instruction in the attached text file in order to keep your computer safe. Virtually yours, The ogf.org team.

1 0

Returned mail: see transcript for details
by Returned mail 08 Sep '06

08 Sep '06

Your message was undeliverable due to the following reason: Your message was not delivered because the destination server was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message could not be delivered within 7 days: Host 142.55.116.131 is not responding. The following recipients could not receive this message: <jsdl-wg(a)ogf.org> Please reply to postmaster(a)ogf.org if you feel this message to be in error.

1 0

POSIXApplication Limits
by Peter G. Lane 07 Sep '06

07 Sep '06

I'm confused about many of the limits in POSIXApplication. Some seem redundant with respect to the Resources requirement elements. Other's simply don't seem clear in their spec descriptions. In general, it seems unclear whether "job" refers to the entire job or a single process. For example, MemoryLimit says "...the maximum amount of physical memory that the job should use when executing", whereas CPUTimeLimit says "...the number of CPU time seconds a job is allowed to consume before a SIGXCPU signal is sent to the job". In the first case I would interpret "job" to mean the one or more processes a job spawns in the process of achieving completion. In the second case it seems that "job" means an individual process. Is it then impossible to specify a total job CPU limit for all processes, or is that what TotalCPUTime in Resources is meant for? But then it's not so clear why MemoryLimit is not redundant with TotalPhysicalMemory. Here are some more specific questions: WallTimeLimit -- Why isn't there a hard wall time limit if this is a soft limit? DataSegmentLimit -- What is meant by a data segment? VirtualMemoryLimit -- Similar to MemoryLimit, what's the difference between this and an UpperBoundedRange value for Resources' TotalVirtualMemory? Is there some reason someone would want to request nodes with a total virtual memory capacity greater than they are limiting their job to use? Thanks! Peter

3 4

Update to HPC Profile Application draft
by Christopher Smith 07 Sep '06

07 Sep '06

I've posted an update for the HPC Profile Application extension to gridforge. https://forge.gridforum.org/sf/go/doc13735?nav=1 I've incorporated Donal's edits, and have made other edits due to his comments. Three items are still open for discussion: 1. Behaviour when WorkingDirectory is specified, but the directory doesn't exist. I've added text to say that this should cause a fault to be raised. 2. Relationship between WallClockLimit and JSDL Resources section. I've added text that the WallClockLimit may be used by the consuming system as part of the resource selection criteria. 3. Format for directory and file names. Which delimiter is to be accepted? For fully qualified path names, I guess we should accept "drive letter qualified" paths (e.g. c:\my\directory\path) in addition to simple delimiter started paths. Should UNC path names be accepted? I would propose to add text accepting '/' as a delimiter, and allowing all three of the above for fully qualified paths. -- Chris

2 1