- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- SMTP receive sequence and status
Operating System - OpenVMS
1748288
Members
3371
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 06:54 PM
тАО07-19-2007 06:54 PM
I notice that image accounting shows LOGINOUT exiting with a status of %X0 at the beginning of every conversation with a sending node. Is this the expected behavior, or did someone forget that 1 is the standard exit on VMS and not 0.
First is LOGINOUT with an exit of %X0.
Next, SET with an exit of %X10000001
Then DELETE with an %X10000001
Next TCPIP$SMTP_RECEIVER.EXE with an %X1
Finally, LOGINOUT.EXE with %X10000001
First is LOGINOUT with an exit of %X0.
Next, SET with an exit of %X10000001
Then DELETE with an %X10000001
Next TCPIP$SMTP_RECEIVER.EXE with an %X1
Finally, LOGINOUT.EXE with %X10000001
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-19-2007 09:38 PM
тАО07-19-2007 09:38 PM
Solution
May be because loginout is not run as an image (don't know how to call it) ?
When you do logout it runs as an image and exits normaly.
When you do run/det RUNDET.exe is acticated that will run loginout in the newly created process. Here it exits with 0 too.
When it runs in a process context to initialize the process (as requested by job control) it could conform to other standards.
Fwiw
Wim
When you do logout it runs as an image and exits normaly.
When you do run/det RUNDET.exe is acticated that will run loginout in the newly created process. Here it exits with 0 too.
When it runs in a process context to initialize the process (as requested by job control) it could conform to other standards.
Fwiw
Wim
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2007 01:07 AM
тАО07-20-2007 01:07 AM
Re: SMTP receive sequence and status
There are two issues, and yes, that status does look a little weird though loginout is itself a seriously weird image; its goal is to set up the DCL environment. The rundown implicit in its image exit already has implications for temporary identifiers, too. There are other oddities. (My guess? Somebody missed an exit path.)
The second issue is why TCP/IP needs a DCL-based process to receive an SMTP connection. That looks to be a fairly heavyweight and more complex approach toward receiving a message. DECnet evolved away from this, and allowed direct image activation as part of its server task support.
Not sure I'd class either of these as bugs or as "yep, it does that" cases, and that decision is up to HP in any case. Having an SMTP server start up, and start sucking in all arriving mail would seem a more resource friendly approach -- and current behavior would seem to have a wider effect than an errant R0 exit.
The second issue is why TCP/IP needs a DCL-based process to receive an SMTP connection. That looks to be a fairly heavyweight and more complex approach toward receiving a message. DECnet evolved away from this, and allowed direct image activation as part of its server task support.
Not sure I'd class either of these as bugs or as "yep, it does that" cases, and that decision is up to HP in any case. Having an SMTP server start up, and start sucking in all arriving mail would seem a more resource friendly approach -- and current behavior would seem to have a wider effect than an errant R0 exit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2007 02:23 AM
тАО07-20-2007 02:23 AM
Re: SMTP receive sequence and status
I agree that the entire TCP/IP stack ought to be revisited for performance and security.
Another peeve is how SSH creates you as a "INTERACTIVE" (i.e., local) user, and none of the utilities show the remote host information like LAT used to in $SHOW USER/FULL
My guess is that SSH ought to be an ACP-like process for the SSH protocol, so I do not get 2 processes per connection. I think a more full-featured pseudoterminal like the old YW/PY pair would solve a lot of evils here.
Another peeve is how SSH creates you as a "INTERACTIVE" (i.e., local) user, and none of the utilities show the remote host information like LAT used to in $SHOW USER/FULL
My guess is that SSH ought to be an ACP-like process for the SSH protocol, so I do not get 2 processes per connection. I think a more full-featured pseudoterminal like the old YW/PY pair would solve a lot of evils here.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP