Sponsored Content
Full Discussion: Nonsense error in FORTRAN
Top Forums UNIX for Beginners Questions & Answers Nonsense error in FORTRAN Post 303045977 by RudiC on Monday 20th of April 2020 05:09:35 PM
Old 04-20-2020
My FORTRAN days are looooooong gone, but two of the three "error coordinates" indicate the complier might not be happy with the ^ for exponentiation. I faintly remember it being ** in those old days. Sure you got no syntax gobbledigook?
This User Gave Thanks to RudiC For This Post:
 

4 More Discussions You Might Find Interesting

1. Programming

Error running FORTRAN code

Hi, I am new to this forum and do not know whether this is the appropriate place to post this question. Anyway am trying my luck. I have a fortran program swanhcat.ftn, which is part of a wave modelling system. There is also a file hcat.nml which is required to run this program. The program's... (9 Replies)
Discussion started by: sandhyakg
9 Replies

2. Programming

Fortran runtime error: Insufficient data descriptors in format after reversion

Hello, I have some Fortran code that is providing the following error: At line 1165 of lapc_shells_2.f Fortran runtime error: Insufficient data descriptors in format after reversion Here are the lines just above and including 1165: WRITE (*,"('ATTEMPTING TO READ PLATE... (1 Reply)
Discussion started by: jm4smtddd
1 Replies

3. Homework & Coursework Questions

FORTRAN error *** glibc detected ***

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: I'm doing aproximation of derivative called five-point stencil. For every value of x, in interval , in step... (0 Replies)
Discussion started by: antonija
0 Replies

4. Programming

Error in my FORTRAN program

I have a Fortran program and I am writing out to logical unit 7. The program is reading from a text file and writing to the new file formatted. It gets through the read and writes some to the file but then stops with the following error: 1525-013 The sequential WRITE statement cannot be... (5 Replies)
Discussion started by: KathyB148
5 Replies
shadow(4)						     Kernel Interfaces Manual							 shadow(4)

NAME
shadow - shadow password file SYNOPSIS
DESCRIPTION
The file is created from the file by the command. It is readable only by a privileged user. It can be modified by the and commands. Pro- grams may use the interfaces described in the getspent(3C) manpage to access this information. These functions return a pointer to an structure, which is defined in the header file. Fields The file is an ASCII file consisting of any number of user entries separated by newlines. Each user entry line consists of the following fields separated by colons: login name Each login name must match a login name in puts the user entries in in the same order as the entries. encrypted password The password field of each entry contains an "x", and the actual encrypted passwords reside in The encrypted password field consists of 13 characters chosen from a 64-character set of "digits". The characters used to represent "digits" are for 0, for 1, through for 2 through 11, through for 12 through 37, and through for 38 through 63. If the SHA11i3 product is installed, the password field may contain the prefix , where n is a label identifying an alterna- tive algorithm used for the password hash. Using the new algorithm results in an encrypted password field which is longer than 13 characters. The password field will consist of digits from the same 64-character set, as well as the additional character used as a delimiter. If this field is null, then there is no password and no password is demanded on login. Login can be prevented by entering a character that is not a part of the set of digits (such as *). last change The number of days since January 1, 1970 that the password was last modified. min days The minimum period in days that must expire before the password can be changed. See also in security(4) and the command in passwd(1). max days The maximum number of days for which a password is valid. A user who attempts to login after his password has expired is forced to supply a new one. If min days and max days are both zero, the user is forced to change his password the next time he logs in. If min days is greater than max days, then the password cannot be changed. These restrictions do not apply to the superuser. See also in security(4) and the command in passwd(1). warn days The number of days the user is warned before his password expires. See also in security(4) and the command in passwd(1). inactivity The maximum number of days of inactivity allowed. This field is set with the option of either the or command. If this value is greater than zero, then the account is locked if there have been no logins to the account for at least the specified num- ber of days. If this value is less than or equal to zero, the value is determined by the attribute. See the description of in security(4). expiration The absolute number of days since Jan 1, 1970 after which the account is no longer valid. A value of zero in this field indicates that the account is locked. reserved The reserved field is always zero and is reserved for future use. Notes The file is not applicable to a system which has been converted to a trusted system. WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. FILES
system password file shadow password file SEE ALSO
login(1), passwd(1), pwconv(1M), pwunconv(1M), useradd(1M), userdel(1M), usermod(1M), crypt(3C), getspent(3C), putspent(3C), nss- witch.conf(4), passwd(4), security(4). shadow(4)
All times are GMT -4. The time now is 12:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy