- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- System Login Flow
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
06-12-2007 02:36 AM
06-12-2007 02:36 AM
System Login Flow
"System checks whether SYS$LOGIN is defined.
If SYS$LOGIN is defined, the logical name is translated (in the case of DCL, to SYS$MANAGER:SYLOGIN.COM) and that procedure executes. If SYS$SYLOGIN is not defined, no system login is run."
But SYS$LOGIN does not translate to that, it translates to the user's home directory.
I do have SYS$SYLOGIN defined, but it translates to SYS$MANAGER:SYS$SYLOGIN.COM (custom I'm sure).
The trouble is, there also is a SYLOGIN.COM which would appear to run as well ... trying to figure out how it gets invoked.
Or does the above statement just have too many words (if you leave out the "in the case of DCL") .. if SYS$LOGIN is defined, then it executes SYS$MANAGER:SYLOGIN.COM ?
Obviously I'm missing something (again)!
Cheers,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:05 AM
06-12-2007 03:05 AM
Re: System Login Flow
Sys$login is the logical name for a users login directory.
Sys$sylogin, if defined, is the logical name for the system-wide login procedure, which is normaly sys$manager:sylogin.com
If sys$sylogin is undefined, the system executes sys$manager:sylogin.com as well.
The protection of those files may also be important (W:RE)
hope that helps
regards
Geni
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:22 AM
06-12-2007 03:22 AM
Re: System Login Flow
http://h71000.www7.hp.com/doc/73final/6017/6017pro_014.html
Shankar
********************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:29 AM
06-12-2007 03:29 AM
Re: System Login Flow
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:47 AM
06-12-2007 03:47 AM
Re: System Login Flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2007 03:51 AM
06-12-2007 03:51 AM
Re: System Login Flow
Wim