Should password file entries show as machine+user
Kertz, Denis (D)** CTR **
Fri May 15 06:52:00 GMT 2015
We have a new desktop PC with Windows 7 Professional installed. Corporate IT had to set it up with a domain to allow access to the corporate intranet. We have installed cygwin 64-bit:
$ uname -a
CYGWIN_NT-6.1 <machine> 2.0.2(0.287/5/3) 2015-05-08 17:00 x86_64 Cygwin
On initial access, there was no passwd file so it was created by: mkpasswd -l >/etc/passwd
Checking the passwd file, we were surprised to see the login entry as <machine>+login:
Running mkpasswd with -l -d or -l -c options gives the same results.
We compared this with an older but identical desktop model also running Win7 Pro with cygwin 64-bit
$ uname -a
CYGWIN_NT-6.1 <machine> 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 Cygwin
and its password entry is just plain login (no <machine>+):
So far it isn't obvious there is anything wrong here. We have been able to setup cron (using /usr/bin/cron-config). Initially, cron failed and /usr/bin/cronevents said it couldn't switch user context. Checking the Win7 services.msc showed Cron was setup to use the local system account. When we changed that to use the above login (copying the setup of the older PC) a simple cron job worked.
Nevertheless, we are uneasy with this <machine>+user entry since it differs from the older PC/cgwin setup. It is also rather annoying that file permissions (ls -l) show both the owner and the group prefixed with <machine>+ and which clutter the output.
Anybody know whether this should be a concern (we can live with the cluttered file permissions if that is the only issue)? Could it be the later version of gywin (2.0.2 vs 1.7.32) is the reason for this difference? Or could the corporate IT have messed up the configuration and there is something we need to get fixed (if so, what)?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin