Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : MSFT Internet Explorer vs. NSCP Navigator -- Ignore unavailable to you. Want to Upgrade?

To: Justin Banks who wrote (17650)	2/25/1998 2:12:00 PM
From: d[-_-]b	Respond to of 24154

Yes, from NT I would like to have a command: chpasswd -NT MAD1 MAD2 -NIS nis1 nis2 Assuming the above you have two NT domain and two UNIX nis domains, further assuming all passwds are currently the same and the same username on each domain, this routine would in turn change your passwd on each domain so they would be in sync. I currently have a routine that will do the NT side of things, but nothing to contact a UNIX NIS rpc.yppasswd daemon. So what I started writing was a daemon to run on each UNIX NIS master that could be contacted via simple sockets (i.e. like telnet hostname 110, for pop3) and have the daemon on UNIX running with the appropriate suid bits as root to actually change a users passwd without actually logging into UNIX. The problem is yppasswd and passwd don't want to run without a "real" tty, however using perl, I can fake out those programs and let my dumb daemon hold the conversation with the remote chpasswd program, then invoke a perl script to do the real yppasswd work.