Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Brian E. Aydemir" <baydemir@cis.upenn.edu>
To: Pietro Abate <Pietro.Abate@anu.edu.au>
Cc: ocaml ml <caml-list@inria.fr>
Subject: Re: [Caml-list] getlogin : no such file or directory ??
Date: Thu, 12 Apr 2007 08:06:09 -0400	[thread overview]
Message-ID: <E2358F94-DA93-4660-BB7C-1A535824B3F5@cis.upenn.edu> (raw)
In-Reply-To: <20070412085007.GA9614@pulp.rsise.anu.edu.au>

On Apr 12, 2007, at 4:50 AM, Pietro Abate wrote:

> why the Unix.getlogin function returns "no such file or directory"
> if the unix getlogin() function returns null (see getlogin.c) ?
>
> ex:
> -----------
> let main () =
>   try
>       print_string (Unix.getlogin())
>   with Unix.Unix_error(e,_,_) ->
>       failwith (Unix.error_message e)
> ;;
>
> main ()
> ---------
>
> echo "a" | ./a.out
> Fatal error: exception Failure(No such file or directory")
>
> How can I use getlogin if I want to pass something on the standard  
> input
> to my program ?
>
> The same example works with MacOsX. Why this difference ?

It looks like OCaml simply calls the operating system's  
implementation of getlogin().  I ran into a similar issue with Python  
code a while back, so that's where my experience with this comes from.

The problem is that it seems not all Unix-like operating systems  
implement getlogin() in exactly the same way.  For example, getlogin 
() under Linux dies with the "No such file or directory" error when  
standard-in is not a terminal.  getlogin() under Mac OS X doesn't  
seem to care what standard-in is.  The man pages for getlogin might  
say something about this, as well.

My solution was to use getpwuid(getuid()) instead of getlogin().

Cheers,
Brian


      reply	other threads:[~2007-04-12 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12  8:50 Pietro Abate
2007-04-12 12:06 ` Brian E. Aydemir [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E2358F94-DA93-4660-BB7C-1A535824B3F5@cis.upenn.edu \
    --to=baydemir@cis.upenn.edu \
    --cc=Pietro.Abate@anu.edu.au \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox