Re: Very strange behavior of ls & user groups

[Unix Tools]

Hi,
In every virtualhost please try the User directive.
User 
And enable apache suexec. This is the most secured way to run apache.

Cheers


- Original Message - 
From: "Dmitry Popov" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 05:18 AM
Subject: Very strange behavior of ls & user groups


> Greetings!
> 
> I've got some odd problems with FreeBSD 4.5:
> 
> 1. invocation of "ls -l" or other programs like "tar tvzf", that seems
> to be use the same output library, causes a core dump. althrough, "ls"
> and "tar xvzf" work fine. are there any ways to fix the problem without
> rebuilding whole system?
> 
> 2. apache has its own group and each client, that needs access via HTTP,
> has its own group and apache as group guest (then apache can read user's
> files while other users can not). the problem: it seems to be, user
> (apache) can't be guest in more than 14 groups. is there any workarounds
> and reasons for such kind of limitations?
> 
> great thanks for help and advices!
> 
> please respond to [EMAIL PROTECTED]
> 
> 
> --
>   Best regards, Dmitry Popov
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
> 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Very strange behavior of ls & user groups

[Mike Meyer]

In <[EMAIL PROTECTED]>, Dmitry Popov <[EMAIL PROTECTED]> typed:
> I've got some odd problems with FreeBSD 4.5:

It really is best to limit yourself to one problem per message, with
an appropriate subject.

> 1. invocation of "ls -l" or other programs like "tar tvzf", that seems
> to be use the same output library, causes a core dump. althrough, "ls"
> and "tar xvzf" work fine. are there any ways to fix the problem without
> rebuilding whole system?

Have you tried building the unstripped version of ls and seeing what
the problem is? You may be able to limit what you have to rebuild to
just the library in question. Possibly it's something strange in your
environment, and changing that will solve the problem. But until you
know which library is causing the problem, there's not much you can do
other than rebuild everything.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message