cuserid returns original login after a su to another user

[Richard]

Perhaps you think that because your off topic answers are always
complete and correct, and nothing could be gained by asking them in
the proper forum.

Did you read what I said? Again for your
edification and delight:


If you don't agree fine. But kindly don't tell me what I may and may not
write if I think it is constructive and helpful.

OTOH, this is a problem for the rest of us. As the world learns about
your omniscience and infallibility, they will all come here with their
off topic questions, and there won't be time and space for topical
questions.

I have no idea what you are raving about. Or are you just being an
arrogant prick?

 

[jmcgill]

Use geteuid() / getuid() combined with a getpwent().

That's POSIX, among other things, not ANSI C.

 

[Al Balmer]

Did you read what I said? Again for your
edification and delight:



If you don't agree fine. But kindly don't tell me what I may and may not
write if I think it is constructive and helpful.

I think it's you who are not reading. I did not tell you what not to
write. (However, you seem to be telling me what not to write.) I was
simply speculating on your reason for not agreeing with the obvious
reasons for not "mentioning possible solutions" to off-topic
questions. When you do so, you are not really doing the questioner any
favors. If you really think you have the answer, redirect the
questioner, then go to that forum and answer it there, where your
answer can be peer-reviewed and possibly even improved upon.

I have no idea what you are raving about.

Try re-reading it, slowly and carefully.

Or are you just being an
arrogant prick?

If you like.

 

[Keith Thompson]

If someone thinks its a C question, asks here it never hurts to mention
a possible solution at the same time as pointing them out to better
resources. I'm surprised anyone would think any different.

Here's the problem: Some of us here are experts on standard C. Fewer
of us are experts on Unix and POSIX. Worse, some of us might *think*
we're experts on Unix and POSIX even if we're not.

Suppose somebody asks a question that turns out to be Unix-specific.
I post a followup:

Sorry, standard C doesn't have that feature. Try
comp.unix.programmer -- but in the meantime, I think the
getfoobar() function will solve your problem.

Then somebody else posts a correction:

The getfoobar() function is Linux-specific; didn't the OP say he
was using Solaris?

and another:

Actually, getfoobar() is supported on Solaris 10.

And yet another:

The Solaris getfoobar() function is subtly different from the
Linux getfoobar() function. Here are the gory details. [...]
But on any POSIX system, you can achieve the same affect with
getfoo(getbar(getuid())). Oh, wait, you need to use getruid(),
unless it's after dark on a Tuesday

and it finally turns out that I misunderstood the OP's actual problem,
and the whole discussion has been off-topic *and* a waste of time.

Or, I post a followup to the original post:

Sorry, standard C doesn't have that feature.
Try comp.unix.programmer.

and the OP goes off to a forum filled with experts on Unix
programming, and gets a quick, useful, and correct solution to his
prpblem, and we can spend our time here talking about standard C.

See the difference?

 

[Richard Heathfield]

Keith Thompson said:

Here's the problem: Some of us here are experts on standard C. Fewer
of us are experts on Unix and POSIX. Worse, some of us might *think*
we're experts on Unix and POSIX even if we're not.

Suppose somebody asks a question that turns out to be Unix-specific.
I post a followup:

Sorry, standard C doesn't have that feature. Try
comp.unix.programmer -- but in the meantime, I think the
getfoobar() function will solve your problem.

Then somebody else posts a correction:

<bad scenario snipped>

Or, perhaps, somebody else /doesn't/ post a correction, and the OP is left
with the wrong answer. Either way, the OP loses.