Thanks to John Ferlan for the below information.
>This problem is fixed in a patch kit (Patchkit 7 for Tru64 4.0D)
>
>To "work around" the problem :
> 1. Using edauth modify the account with the message "Password about
>to expire" and change the "u_succhg" to have a more recent timestamp (I
>generally just copy the number from "u_suclog")....
>
> 2. Reduce the value of the default system wide notification of about
>to expire in /etc/auth/system/defaults (see the man page for default and
>the d_pw_expire_warning value.
Original question follows:
Since upgrading to Tru64 4.0D PK6 from PK3, I have been unable to get
scp or rcp to work. Running under C2 security.
There are notes at deja stating that scp can't handle output to
STDOUT when connecting to a remote server, and give an error message
about "Broken pipe".
ssh login connections work fine. A debug trace of scp shows that it
is failing when the "password will expire" response comes back.
-----
#scp file1.tst node2:/tmp/
Your password will expire on Mon Nov 27 16:17:23 2000
Write failed flushing stdout buffer.
write stdout: Broken pipe
-----
So when I tried to switch to rcp, I get:
tombrand_at_node1> rcp scan.status
node2:/tmp/scan
Your password will expire on Mon Nov 27 16:17:23 2000
This did work before the upgrade. Any ideas/suggestions as to where
to look from here?
Is there some way to disable the "password will expire" output?
--
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Thomas Brand
System Administrator
Boston Medical Center
Email: Tom.Brand_at_bmc.org (work) TomBrand_at_mac.com (private)
Phone: (617) 638-8205
Received on Thu Sep 28 2000 - 19:27:54 NZST