Bug#542024: neko: mysql5 support broken

2009-08-17 Thread KaalH
Package: neko
Version: 1.8.1-1
Severity: important


( I'm using a backported package builded with cowbuilder for lenny, apologizes 
if it's not reproducible on sid. )

the following neko source code :

class Test {
public static function main() {
var cnx = neko.db.Mysql.connect({
host : localhost,
port : 3306,
user : root,
pass : password,
socket : /var/run/mysqld/mysqld.sock,
//socket : null,
database : test
});
cnx.close();
}
}

produce :

Called from null line 1
Called from Test.hx line 3
Called from neko/db/Mysql.hx line 193
Uncaught exception - mysql.c(444) : Failed to connect to mysql server : Unix 
Socket connections are not supported

or if not using socket :

Called from null line 1
Called from Test.hx line 3
Called from neko/db/Mysql.hx line 193
Uncaught exception - mysql.c(444) : Failed to connect to mysql server : Access 
denied for user 'root'@'localhost' (using password: YES)

deleting /usr/lib/neko/mysql5.ndll fix this issue.


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc3-tip (SMP w/7 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages neko depends on:
ii  libc6  2.7-18GNU C Library: Shared libraries
ii  libglib2.0-0   2.16.6-2  The GLib library of C routines
ii  libmysqlclient15off5.0.51vixns-3 MySQL database client library
ii  libneko0   1.8.1.vixns-1 Lightweight virtual machine - shar
ii  libpcre3   7.6-2.1   Perl 5 Compatible Regular Expressi
ii  libsqlite3-0   3.5.9-6   SQLite 3 shared library
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

neko recommends no packages.

Versions of packages neko suggests:
pn  libapache2-mod-neko   none (no description available)
pn  neko-dev  none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#240685: runit-run: .

2006-04-15 Thread KaalH!
Package: runit-run
Version: 0.7.0
Followup-For: Bug #240685


Could you please upgrade runit-policy-rc.d by allowing the action when the 
target script is a link to the sv binary ?

Thanks,
kaalh

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (33, 'unstable'), (15, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.26-vs1.3.8-2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages runit-run depends on:
ii  runit1.3.3-1 a UNIX init scheme with service su
ii  sysv-rc  2.86.ds1-13 System-V-like runlevel change mech

Versions of packages runit-run recommends:
pn  fgettynone (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#317557: yaws: missing mime types

2005-07-09 Thread KaalH!
Package: yaws
Version: 1.54-1
Severity: normal


the mime.types file included in yaws sources is really old.
some usefull types are missing (eg: most *msvideo* types)
please add mime types to yaws' mime.types file or use /etc/mime.types on
deb building.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (33, 'unstable'), (15, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.11
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages yaws depends on:
ii  erlang  1:10.b.5-1   A real-time, concurrent and distri
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#316856: awstats: geoip.pm breaks reports for mozilla based browsers.

2005-07-04 Thread KaalH!
Package: awstats
Version: 6.4-1
Severity: normal


replacing br with br / in geoip.pm at line 144 fix the problem.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (33, 'unstable'), (15, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.26-vs1.3.8-2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages awstats depends on:
ii  perl [libstorable-perl]   5.8.7-3Larry Wall's Practical Extraction 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#307719: clamav-daemon: Add support for stderr logging

2005-05-09 Thread KaalH!
Stephen Gran a écrit :

On Fri, May 06, 2005 at 11:24:49AM +0200, KaalH! said:
  

Stephen Gran a écrit :



This one time, at band camp, KaalH! said:

  

please apply this patch to add stderr loggging. This is for multilog/svlogd.
It allows LogFile stderr configuration option


Does
LogFile /dev/stderr 
not work for you?

Just remember to use LogFileUnlock with it :)

  

no

I'm using runit

chpst -uclamav /usr/sbin/clamd

ERROR: Can't open /dev/stderr in append mode (check permissions!).
ERROR: Problem with internal logger. Please check the permissions on the
/dev/stderr file.

ls -aLl /dev/stderr
crw--w  1 kaalh tty 136, 6 May  6 10:17 /dev/stderr

mount
...
none on /dev/pts type devpts (gid=5,mode=620)

adding clamav to tty group and chpst -uclamav:tty /usr/sbin/clamd
produce the same error

my clamd.conf contains

LogFile /dev/stderr
LogFileUnlock
Foreground
LogFileMaxSize 0

my runit script :

#!/bin/sh
exec 21
exec chpst -uclamav /usr/sbin/clamd

if you don't use runit you can reproduce this with
sudo -P -u clamav /usr/sbin/clamd



However:
[EMAIL PROTECTED]:~$ grep LogFile /etc/clamav/clamd.conf
LogFile /dev/stderr
LogFileUnlock
LogFileMaxSize 0

[EMAIL PROTECTED]:~$ sudo /etc/init.d/clamav-daemon start /dev/null
Mon May  9 16:30:35 2005 - +++ Started at Mon May  9 16:30:35 2005
Mon May  9 16:30:35 2005 - clamd daemon 0.84 (OS: linux-gnu, ARCH: i386, CPU: 
i386)
Mon May  9 16:30:35 2005 - Log file size limit disabled.
Mon May  9 16:30:35 2005 - Running as user clamav (UID 106, GID 106)
Mon May  9 16:30:35 2005 - Reading databases from /var/lib/clamav
Mon May  9 16:30:36 2005 - Protecting against 34294 viruses.
Mon May  9 16:30:36 2005 - Unix socket file /var/run/clamav/clamd.ctl
Mon May  9 16:30:36 2005 - Setting connection queue length to 15
Mon May  9 16:30:36 2005 - Archive: Archived file size limit set to 10485760 
bytes.
Mon May  9 16:30:36 2005 - Archive: Recursion level limit set to 5.
Mon May  9 16:30:36 2005 - Archive: Files limit set to 1000.
Mon May  9 16:30:36 2005 - Archive: Compression ratio limit set to 250.
Mon May  9 16:30:36 2005 - Archive support enabled.
Mon May  9 16:30:36 2005 - Archive: RAR support disabled.
Mon May  9 16:30:36 2005 - Archive: Blocking archives that exceed limits.
Mon May  9 16:30:36 2005 - Portable Executable support enabled.
Mon May  9 16:30:36 2005 - Detection of broken executables enabled.
Mon May  9 16:30:36 2005 - Mail files support enabled.
Mon May  9 16:30:36 2005 - OLE2 support enabled.
Mon May  9 16:30:36 2005 - HTML support enabled.
Mon May  9 16:30:36 2005 - Self checking every 3600 seconds.

Seems to be writing to stderr to me.  Perhaps chpst is broken?
  

hoho, there's no start-stop-daemon -u clamav  and/or
start-stop-daemon -c clamav   in /etc/init.d/clamav-daemon, but clamd
runs as clamav user :o

clamd seems to turn himself as clamav user, so it needs to be lanched as
root and not as clamav like i made it with chpst.
Is this correct ?

if so, not using chpst will solve my problem.
I hope there's no security issue doing this ...

thanks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306579: clamav-freshclam: does not use --quiet option within cron script

2005-05-04 Thread KaalH!
Stephen Gran a écrit :

This one time, at band camp, KaalH! said:
  

Stephen Gran a ecrit :


This one time, at band camp, KaalH! said:
  

 you may use /usr/bin/freshclam --quiet instead of 
 /usr/bin/freshclam /dev/null within cron script.


  
 No, that will miss warning messages.  This decision was made on
 purpose.  Is there a reason you want it changed?
  

yes,

freshclam jobs sometimes hang after an update (once or twice a day
with hourly run).  I'm using runit to run cron ( cron -f -l ).  on
another host with the --quiet option, got no hanged freshclam for 2
days.  don't know if it's related, but seems better.



Redirection of output seems hardly likely to hang a process.  Does this
other host that doesn't hang use runit?

  

yes.
I'm using vservers, the other host is a copy running on the same machine.

You see, what's going on is that there are 4 categories of messages
output by freshclam

error goes to stderr
warning goes to stderr
info goes to stdout
verbose goes to stdout

You only get verbose messages if you run -v
Using --quiet suppresses info and warning messages.

So the only way to get warning and error is redirect stdout to
/dev/null, but retain the stderr stream, and not use --quiet.

This is actually fairly standard practice - take a look at logrotate
scripts and the like.  They frequently contain 
/etc/init.d/foo reload  /dev/null

  

hum, you're right about the standard practice, but isn't invoke-rc.d
--quiet foo reload  /dev/null better ?

I think ...freshclam  /dev/null redirect stdout only, and
...freshclam 21  /dev/null redirect stderr to stdout to /dev/null,
am I wrong ?

as a postrotate script.

If you are getting ahngs in freshclam, there is either a problem with
freshclam itself, or with the envirnment calling it.  An investigation
in that direction seems in order.  The redirection of output itself
seems unlikely to cause any harm, unless there is something wierd with
your environment.
  

yes, smthg may be broken.
I'm testing for several days, and the --quiet really makes a
difference, even if I don't know exactly why.

what about ...freshclam --quiet  /dev/null ?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306579: clamav-freshclam: does not use --quiet option within cron script

2005-05-04 Thread KaalH!
Stephen Gran a écrit :

This one time, at band camp, KaalH! said:
  

Stephen Gran a écrit :
hum, you're right about the standard practice, but isn't invoke-rc.d
--quiet foo reload  /dev/null better ?

I think ...freshclam  /dev/null redirect stdout only, and
...freshclam 21  /dev/null redirect stderr to stdout to /dev/null,
am I wrong ?



That is correct.

  

as a postrotate script.

If you are getting ahngs in freshclam, there is either a problem with
freshclam itself, or with the envirnment calling it.  An investigation
in that direction seems in order.  The redirection of output itself
seems unlikely to cause any harm, unless there is something wierd with
your environment.
 

  

yes, smthg may be broken.
I'm testing for several days, and the --quiet really makes a
difference, even if I don't know exactly why.

what about ...freshclam --quiet  /dev/null ?



Again, that misses warning messages.  --quiet eliminates messages at
level verbose, normal, and warning.  I would like the admin to see
messages at level warning and error.  Since warning and error level
messages go to stderr, the script only needs to throw away stdout in
order to achieve the desired effect.

You say you're on a vserver - do you not have /dev/null, or is it
inaccessible to you?  That would be odd, but I suppose it's possible.


Got it !

freshclam hang was related to clamd notification, googling tell about
softlimit trouble with clamd.

I'm actually running clamd with exec chpst -uclamav -m 4000
/usr/sbin/clamd, i will increase this limit and see what happends.

I'm surprising getting trouble with limit to 4000 bytes for just
virus database update notification ( no scanning activity, these are
hopfully dev vservers).

differences between my vservers were due to mistaking clamav database
files permissions, sorry about the noise and thank you for your time,
please close this bug.






-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#307719: clamav-daemon: Add support for stderr logging

2005-05-04 Thread KaalH!
Package: clamav-daemon
Version: 0.83-5
Severity: wishlist


please apply this patch to add stderr loggging. This is for multilog/svlogd.
It allows LogFile stderr configuration option

thanks


diff -ru clamav-0.84/clamd/clamd.c clamav-0.84-new/clamd/clamd.c
--- clamav-0.84/clamd/clamd.c   2005-04-20 01:33:13.0 +0200
+++ clamav-0.84-new/clamd/clamd.c   2005-05-04 22:52:13.0
+0200
@@ -137,8 +137,13 @@
 if((cpt = cfgopt(copt, LogFile))) {
logg_file = cpt-strarg;
if(strlen(logg_file)  2 || (logg_file[0] != '/'  logg_file[0] != 
'\\'  logg_file[1] != ':')) {
-   fprintf(stderr, ERROR: LogFile requires full path.\n);
-   exit(1);
+   if (strcmp(logg_file,stderr)!=0) {
+  fprintf(stderr, ERROR: LogFile requires full path.\n);
+  exit(1);
+   }
+   else {
+   use_stderr=1;
+   }
}
time(currtime);
if(logg(+++ Started at %s, ctime(currtime))) {
diff -ru clamav-0.84/shared/output.c clamav-0.84-new/shared/output.c
--- clamav-0.84/shared/output.c 2005-04-20 01:33:15.0 +0200
+++ clamav-0.84-new/shared/output.c 2005-05-04 22:50:01.0
+0200
@@ -115,7 +115,9 @@
 #ifdef CL_THREAD_SAFE
pthread_mutex_lock(logg_mutex);
 #endif
-   if(!logg_fd) {
+   if(use_stderr) {
+   logg_fd = stderr;
+   } else if(!logg_fd) {
old_umask = umask(0037);
if((logg_fd = fopen(logg_file, a)) == NULL) {
umask(old_umask);
@@ -150,7 +152,7 @@
free(timestr);
}

-   if(logg_size) {
+   if(logg_size  !use_stderr) {
if(stat(logg_file, sb) != -1) {
if(sb.st_size  logg_size) {
logg_file = NULL;
diff -ru clamav-0.84/shared/output.h clamav-0.84-new/shared/output.h
--- clamav-0.84/shared/output.h 2005-04-20 01:33:15.0 +0200
+++ clamav-0.84-new/shared/output.h 2005-05-04 22:50:01.0
+0200
@@ -28,6 +28,7 @@

 int mdprintf(int desc, const char *str, ...);

+int use_stderr;
 int logg(const char *str, ...);
 void logg_close(void);
 extern short int logg_verbose, logg_lock, logg_time;




-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (33, 'unstable'), (15, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages clamav-daemon depends on:
ii  clamav-base 0.83-5   base package for clamav, an anti-v
ii  clamav-freshclam [clamav-da 0.83-5   downloads clamav virus databases f
ii  libbz2-1.0  1.0.2-5  high-quality block-sorting file co
ii  libc6   2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libclamav1  0.83-5   virus scanner library
ii  libcurl37.13.2-2 Multi-protocol file transfer libra
ii  libgmp3 4.1.4-6  Multiprecision arithmetic library
ii  libidn110.5.13-1.0   GNU libidn library, implementation
ii  libssl0.9.7 0.9.7e-3 SSL shared libraries
ii  zlib1g  1:1.2.2-4compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306898: approx: detach option proposal

2005-04-29 Thread KaalH!
Package: approx
Version: 1.12
Severity: wishlist


runit based systems requires to not detach daemon.
see my hack below.


diff -ru approx-1.12/approx.conf approx-1.12new/approx.conf
--- approx-1.12/approx.conf 2005-04-17 18:50:49.0 +0200
+++ approx-1.12new/approx.conf  2005-04-29 09:57:29.0 +0200
@@ -5,6 +5,7 @@
 #cache /var/cache/approx
 #interval  720
 #debug false
+#detachtrue

 # Here are some examples of remote repository mappings.

diff -ru approx-1.12/approx.conf.5 approx-1.12new/approx.conf.5
--- approx-1.12/approx.conf.5   2005-04-08 20:59:28.0 +0200
+++ approx-1.12new/approx.conf.52005-04-29 09:58:34.0
+0200
@@ -35,6 +35,10 @@
 Specifies whether debugging messages should be printed
 (default:
 .BR false )
+.IP detach
+Specifies whether detaching approx daemon
+(default:
+.BR true )
 .PP
 The other name/value pairs  are used to map distribution names
 to remote repositories.  For example,
diff -ru approx-1.12/approx.ml approx-1.12new/approx.ml
--- approx-1.12/approx.ml   2005-04-25 15:54:00.0 +0200
+++ approx-1.12new/approx.ml2005-04-29 09:45:02.0 +0200
@@ -339,6 +339,11 @@
   message %s (Printexc.to_string e)

 let () =
-  (* double fork to detach daemon *)
-  if Unix.fork () = 0  Unix.fork () = 0 then
-daemon ()
+  if detach then
+  begin
+  (* double fork to detach daemon *)
+  if Unix.fork () = 0  Unix.fork () = 0 then
+  daemon ()
+  end
+  else
+  daemon ()
diff -ru approx-1.12/default_config.ml approx-1.12new/default_config.ml
--- approx-1.12/default_config.ml   2005-04-08 20:59:28.0
+0200
+++ approx-1.12new/default_config.ml2005-04-29 02:26:12.0
+0200
@@ -12,3 +12,4 @@
 let port = get_int port ~default: 
 let interval = get_int interval ~default: 720 (* minutes *)
 let debug = get_bool debug ~default: false
+let detach = get_bool detach ~default: true
diff -ru approx-1.12/default_config.mli
approx-1.12new/default_config.mli
--- approx-1.12/default_config.mli  2005-04-08 20:59:28.0
+0200
+++ approx-1.12new/default_config.mli   2005-04-29 02:25:59.0
+0200
@@ -7,3 +7,4 @@
 val port : int
 val interval : int
 val debug : bool
+val detach : bool


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (33, 'unstable'), (15, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages approx depends on:
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libcurl37.13.2-2 Multi-protocol file transfer libra
ii  libidn110.5.13-1.0   GNU libidn library, implementation
ii  libpcre34.5-1.1  Perl 5 Compatible Regular Expressi
ii  libssl0.9.7 0.9.7e-3 SSL shared libraries
ii  wget1.9.1-8  retrieves files from the web
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#306579: clamav-freshclam: does not use --quiet option within cron script

2005-04-28 Thread KaalH!




Stephen Gran a crit:

  This one time, at band camp, KaalH! said:
  
  
you may use "/usr/bin/freshclam --quiet" instead of " /usr/bin/freshclam


  /dev/null" within cron script.
  

  
  
No, that will miss warning messages.  This decision was made on purpose.

Is there a reason you want it changed?
  

yes,

freshclam jobs sometimes hang after an update (once or twice a day with
hourly run).
I'm using runit to run cron ( cron -f -l ).
on another host with the --quiet option, got no hanged freshclam for 2
days.
don't know if it's related, but seems better.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]