Greetings, Larry Hall (Cygwin)!
This takes 7.1 seconds on my system, with a 12-line /etc/passwd file:
#include
#include
#include
int main(int argc, const char* argv[])
{
int i;
const char* user =
On 2/7/2014 5:45 PM, David Stacey wrote:
On 07/02/14 21:44, Larry Hall (Cygwin) wrote:
On 2/7/2014 3:09 PM, Warren Young wrote:
This takes 7.1 seconds on my system, with a 12-line /etc/passwd file:
#include
#include
#include
int main(int argc, const char* argv[])
On 07/02/14 21:44, Larry Hall (Cygwin) wrote:
On 2/7/2014 3:09 PM, Warren Young wrote:
This takes 7.1 seconds on my system, with a 12-line /etc/passwd file:
#include
#include
#include
int main(int argc, const char* argv[])
{
int i;
const cha
> I think SAM/AD will be mostly quicker
I do not want to be a party pooper here, but have you checked how
the AD approach will work from the unmanaged Windows service accounts?
We've been experiencing rather nasty effects of the M$ design that
when a host changes its password (it is required to,
On 2/7/2014 3:09 PM, Warren Young wrote:
This takes 7.1 seconds on my system, with a 12-line /etc/passwd file:
#include
#include
#include
int main(int argc, const char* argv[])
{
int i;
const char* user = argv[1];
if (!user) {
On Feb 7 13:09, Warren Young wrote:
> On 2/7/2014 02:49, Corinna Vinschen wrote:
> >On Feb 6 14:43, Warren Young wrote:
> >>On 2/6/2014 07:13, Corinna Vinschen wrote:
> >
> >it would, of course, be possible to implement Cygwin
> >command line tools along the lines of useradd/usermod/groupdel. Fo
On Feb 7 13:25, Warren Young wrote:
> On 2/7/2014 13:09, Warren Young wrote:
> >
> >I want getpwent() and friends to remain available, but to switch to
> >AD/SAM as primary, like OS X does all the time,
>
> I just realized that this means getpwent() turns into an AD database
> linear scan at AD s
On 2/7/2014 13:09, Warren Young wrote:
I want getpwent() and friends to remain available, but to switch to
AD/SAM as primary, like OS X does all the time,
I just realized that this means getpwent() turns into an AD database
linear scan at AD sites.
Hmmm...
I think I'm still in favor of the
On 2/7/2014 02:49, Corinna Vinschen wrote:
On Feb 6 14:43, Warren Young wrote:
On 2/6/2014 07:13, Corinna Vinschen wrote:
it would, of course, be possible to implement Cygwin
command line tools along the lines of useradd/usermod/groupdel. For AD,
they would just have to use LDAP,
If by "us
On Feb 7 10:51, Warren Young wrote:
> On 2/7/2014 06:53, David Stacey wrote:
> >On 07/02/2014 09:49, Corinna Vinschen wrote:
> >>On Feb 6 14:43, Warren Young wrote:
> >>>I know a guy who currently has all of
> >>>Cygwin downloaded and ready to re-install, to test this.:)
> >>Try this: strings -f
Greetings, Warren Young!
>> LDAP IS simple.
> Anything tied to a PKI is going to be pretty complex, no matter how
> simple the underlying tech is.
> Then there's the fact that LDAP derives from X.500, a prototypically
> overengineered OSI emission. DC=my,DC=sub,DC=domain,DC=com. P'tui!
Well
On 2/7/2014 06:53, David Stacey wrote:
On 07/02/2014 09:49, Corinna Vinschen wrote:
On Feb 6 14:43, Warren Young wrote:
I know a guy who currently has all of
Cygwin downloaded and ready to re-install, to test this.:)
Try this: strings -f/bin/*.exe/bin/*.dll | grep getgrent
Let me save you
On 2/7/2014 05:49, Andrey Repin wrote:
LDAP IS simple.
Anything tied to a PKI is going to be pretty complex, no matter how
simple the underlying tech is.
Then there's the fact that LDAP derives from X.500, a prototypically
overengineered OSI emission. DC=my,DC=sub,DC=domain,DC=com. P'tui
Greetings, Steven Bardwell!
> I found the problem that was causing the failure of child creation logic
> on the 64-bit install but not on the 32-bit version:
> in an effort to make the output from 'ps' more useful, my application was
> over-writing the contents of argv[1] in the main process. Th
On 07/02/2014 09:49, Corinna Vinschen wrote:
On Feb 6 14:43, Warren Young wrote:
On 2/6/2014 07:13, Corinna Vinschen wrote:
Btw., it would be a good idea to get rid of calls to getpwent/getgrent
in future. They*probably* won't do anymore what they were supposed to
do if you don't have pass
> >> On 2/6/2014 8:50 AM, Steven Bardwell wrote:
> >>> Larry - thanks for the link to the source for the spawn() APIs. It
> > works
> >>> perfectly on my 32-bit install (where, as it happens, the fork() issue
> >>> never shows up either).
> >>>
> >>> However, on my 64-bit install, the spawnv() cal
> >> On 2/6/2014 8:50 AM, Steven Bardwell wrote:
> >>> Larry - thanks for the link to the source for the spawn() APIs. It
> > works
> >>> perfectly on my 32-bit install (where, as it happens, the fork() issue
> >>> never shows up either).
> >>>
> >>> However, on my 64-bit install, the spawnv() cal
Greetings, Mike Rushton!
> What about a Secure Shell client to transfer files and to get a secure
> session going, does Cygwin have that ? I see other people's emails
> about ssh but am not sure if this is what I am looking for.
It is.
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 07.02.2014, <1
Greetings, Mike Rushton!
Please don't http://cygwin.com/acronyms/#TOFU
> What would you say to this ?
> I have to use an EDI translator - it runs under windows/dos and had unix
> versions
If it have UNIX version, perhaps, a Cygwin package for it exists, or it can be
compiled.
> I was trying t
Greetings, Corinna Vinschen!
>> In some of these systems, you can edit /etc/foo and run a command to
>> manually sync that content back to the "real" user info DB. (e.g.
>> the BSDs) In others, direct edits to these files are ignored, but
>> the OS syncs a subset of changes to the user info DB t
On Feb 6 14:43, Warren Young wrote:
> On 2/6/2014 07:13, Corinna Vinschen wrote:
> >
> >Btw., it would be a good idea to get rid of calls to getpwent/getgrent
> >in future. They *probably* won't do anymore what they were supposed to
> >do if you don't have passwd/group files.
>
> There must be a
On Feb 7 10:27, Jan Nijtmans wrote:
> 2014-02-06 15:41 GMT+01:00 Corinna Vinschen:
> > Jan, can you please check if SQlite builds *without* defining
> > __BSD_VISIBLE, but adding the following lines to /usr/include/sys/file.h;
>
> That addition makes SQLite build fine again. You can try it easily
2014-02-06 15:41 GMT+01:00 Corinna Vinschen:
> Jan, can you please check if SQlite builds *without* defining
> __BSD_VISIBLE, but adding the following lines to /usr/include/sys/file.h;
That addition makes SQLite build fine again. You can try it easily
by installing the "sqlite3-debug" package and
23 matches
Mail list logo