On Sun, 29 Dec 2002 14:52:09 -0700
Matt Blecha <[EMAIL PROTECTED]> wrote:
> That's right, my fault... I am not ususally paying attention to sticky...
Well, it's very important in case of directories, because only allows owners
to delete their files.
Best regards,
Tomasz Kojm
--
oo
That's right, my fault... I am not ususally paying attention to sticky...
-Matt
Tomasz Kojm wrote:
On Sun, 29 Dec 2002 13:09:27 -0700
Matt Blecha <[EMAIL PROTECTED]> wrote:
It should still, that is what I believe I have for my lock file
location... /tmp is ok 777, but maybe not,
On Sun, 29 Dec 2002 13:09:27 -0700
Matt Blecha <[EMAIL PROTECTED]> wrote:
> It should still, that is what I believe I have for my lock file
> location... /tmp is ok 777, but maybe not, I haven't had issue so far...
/tmp is 1777, where 1 means a sticky bit !
Best regards,
Tomasz Kojm
--
o
It should still, that is what I believe I have for my lock file
location... /tmp is ok 777, but maybe not, I haven't had issue so far...
Enjoy! ;-)
-Matt
Brian Read wrote:
> I will change them to 765 tomorrow and check that it still works.
>
> Thanks for the help.
>
> Brian
>
>
> At 18:53 29/1
I will change them to 765 tomorrow and check that it still works.
Thanks for the help.
Brian
At 18:53 29/12/2002, you wrote:
>No problem, but like I said, be careful when dolling out 777 perms, a
>virus may be the least of your worries then... Perms are still important
>
>Brian Read wrote:
No problem, but like I said, be careful when dolling out 777 perms, a
virus may be the least of your worries then... Perms are still important
Brian Read wrote:
> I'm using the a local socket in /var/lib/clamav/clamd.sock
>
> I've now set the permissons on the /var/lib/clamav to 777, deleted
I'm using the a local socket in /var/lib/clamav/clamd.sock
I've now set the permissons on the /var/lib/clamav to 777, deleted the
socket, and it seems to be working..
Many thanks
Brian
At 20:45 28/12/2002, you wrote:
>OK, now we have to figure out weather or not we're having a problem with
OK, now we have to figure out weather or not we're having a problem with
binding the UNIX or TCP port, what does your config say for TCPSocket
and LocalSocket?
Also 777 for /var/run may not be the best security, 765 is probably
better, but in your /etc/group file, you should add the clamav user
Ok, set /var/run to 777, and that eliminated the error message about
/var/run/clamd.pid
but still get bind() error
>
Sat Dec 28 11:38:22 2002 -> +++ Started at Sat Dec 28 11:38:22 2002
Sat Dec 28 11:38:22 2002 -> Log file size limited to 1048576 bytes.
Sat Dec 28 11:
Check out the clamav.conf file... In the file, there are two locations
you want to check...
The first entry is LocalSocket it set to /tmp/clamd by default. Set this
to somewhere that clamd can write to with its UID/GID. /tmp is the best,
but that requires perms to /tmp.
The second entry is TCP
At 20:15 27/12/2002, you wrote:
>On Fri, 27 Dec 2002 12:38:11 -0700
>Matt Blecha <[EMAIL PROTECTED]> wrote:
>
> > Here's another question... Does the qmailq user have perms to bind to
> > unix or tcp sockets, if it can't bind a unix or tcp socket, that would
> > be why the crash happens... clamd do
On Fri, 27 Dec 2002 12:38:11 -0700
Matt Blecha <[EMAIL PROTECTED]> wrote:
> Here's another question... Does the qmailq user have perms to bind to
> unix or tcp sockets, if it can't bind a unix or tcp socket, that would
> be why the crash happens... clamd does not do very good error reporting
T
Here's another question... Does the qmailq user have perms to bind to
unix or tcp sockets, if it can't bind a unix or tcp socket, that would
be why the crash happens... clamd does not do very good error reporting
to the console See what perms that the qmailq user has to both
/var/run and to
At 18:05 27/12/2002, you wrote:
>On Fri, 27 Dec 2002 16:58:13 +
>Brian Read <[EMAIL PROTECTED]> wrote:
>
> >
> > I am trying to start clamd (from the command line), and it does not
> give me
> > any error messages, but it fails to start, that is it does not appear in
> > the ps -ax list. wher
Also try checking for the clamd.pid file wherever you specified that clamd
should store it clamd will quit without reporting that it did on the
console, but will log the error
Tomasz Kojm wrote:
On Fri, 27 Dec 2002 16:58:13 +
Brian Read <[EMAIL PROTECTED]> wrote:
I a
On Fri, 27 Dec 2002 16:58:13 +
Brian Read <[EMAIL PROTECTED]> wrote:
>
> I am trying to start clamd (from the command line), and it does not give me
> any error messages, but it fails to start, that is it does not appear in
> the ps -ax list. where should I look for an error messages, ort
On Friday 27 December 2002 11:58 am, you wrote:
> I am trying to start clamd (from the command line), and it does not give me
> any error messages, but it fails to start, that is it does not appear in
> the ps -ax list. where should I look for an error messages, ort what might
> be the trouble?
>
I am trying to start clamd (from the command line), and it does not give me
any error messages, but it fails to start, that is it does not appear in
the ps -ax list. where should I look for an error messages, ort what might
be the trouble?
It was starting yesterday, something seems to have ch
18 matches
Mail list logo
