headers
Dimitrios | 1 May 2004 01:37

Re: Sylpheed-claws gtk2 - new packages?

On Fri, 30 Apr 2004 20:47:30 +0200 (CEST) "Andrzej Nowak" <epsil0n <at> hetman.loiv.torun.pl> wrote:

> It's a build from February. I have no idea how I came across this package...

if i had the .spec file, then i could produce daily CVS snapshots, since
i'm already doing that for gaim. though gaim has a spec file ready and
the sylpheed-claws .spec file is broken.

> right now it's my main mail program. As I mentioned earlier, there are
> several issues which cause the binary to be somewhat less usable than one
> might expect (ie. broken filter box input, address book freezes, other). I
> don't know whether it's caused by porting to gtk2 or by bugs in sylpheed /
> sylpheed-claws code.

i've been using sylpheed-claws for several years now, the problems you
mention must be specific to the GTK2 port since they dont exist in mine.

still, i'd love to move to GTK2 since sylpheed-claws is the very last
GTK1 application, which sort of looks ugly and behaves differently
than the other apps which are GTK2.

> I'd like to have a recent version of sylpheed-claws ported this way... :)
> Sylpheed in GTK2 can easily replace evolution, which is too simple for many
> users, but good-looking.

if only i had a working .spec file... :}
Permalink | Reply | 0 comments |
headers
Andy Grimberg | 1 May 2004 07:35

ClamAV 0.70

The version of ClamAV available in the repo is 0.70-rc Are we going to
see the final version of 0.70?  I'm only asking as freshclam is telling
me that the engine, really, really needs to be updated.  In particular:

--[cut]--
ClamAV update process started at Fri Apr 30 22:33:43 2004
Reading CVD header (main.cvd): OK
main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
tkojm)
Reading CVD header (daily.cvd): OK
daily.cvd is up to date (version: 297, sigs: 1140, f-level: 2, builder:
ccordes)
WARNING: Your ClamAV installation is OUTDATED - please update
immediately !
WARNING: Current functionality level = 1, required = 2
--[/cut]--

According to the FAQ on www.clamav.net this indicates an extreme need to
upgrade the engine.

-Andy-
Permalink | Reply | 121 comments |
headers
Dag Wieers | 1 May 2004 15:41
Favicon
Gravatar

Re: ClamAV 0.70

On Fri, 30 Apr 2004, Andy Grimberg wrote:

> The version of ClamAV available in the repo is 0.70-rc Are we going to
> see the final version of 0.70?  I'm only asking as freshclam is telling
> me that the engine, really, really needs to be updated.  In particular:
> 
> --[cut]--
> ClamAV update process started at Fri Apr 30 22:33:43 2004
> Reading CVD header (main.cvd): OK
> main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
> tkojm)
> Reading CVD header (daily.cvd): OK
> daily.cvd is up to date (version: 297, sigs: 1140, f-level: 2, builder:
> ccordes)
> WARNING: Your ClamAV installation is OUTDATED - please update
> immediately !
> WARNING: Current functionality level = 1, required = 2
> --[/cut]--
> 
> According to the FAQ on www.clamav.net this indicates an extreme need to
> upgrade the engine.

The latest version has been in the repository since it was released.

	[dag <at> emyn dag]# apt-cache policy clamav
	clamav:
	  Installed: 0.70-1.rhfc1.dag
	  Candidate: 0.70-1.rhfc1.dag
	  Version Table:
	 *** 0.70-1.rhfc1.dag 0
(Continue reading)

Permalink | Reply | 107 comments |
headers
Andy Grimberg | 1 May 2004 17:29

Re: ClamAV 0.70

Ahh, I see.  Didn't know about that command (I suppose I should real
_all_ the way through the man pages)

Looks like kde-redhat.org is giving itself a slightly higher preference
for some reason.  I'm getting a preference of 996 for it's clam packages
:/.  Well, it's out of my sources.list now as I don't need KDE stuff on
my server that doesn't have X.

Thanks :)
-Andy-

On Sat, 2004-05-01 at 06:41, Dag Wieers wrote:
> On Fri, 30 Apr 2004, Andy Grimberg wrote:
> 
> > The version of ClamAV available in the repo is 0.70-rc Are we going to
> > see the final version of 0.70?  I'm only asking as freshclam is telling
> > me that the engine, really, really needs to be updated.  In particular:
> > 
> > --[cut]--
> > ClamAV update process started at Fri Apr 30 22:33:43 2004
> > Reading CVD header (main.cvd): OK
> > main.cvd is up to date (version: 22, sigs: 20229, f-level: 1, builder:
> > tkojm)
> > Reading CVD header (daily.cvd): OK
> > daily.cvd is up to date (version: 297, sigs: 1140, f-level: 2, builder:
> > ccordes)
> > WARNING: Your ClamAV installation is OUTDATED - please update
> > immediately !
> > WARNING: Current functionality level = 1, required = 2
> > --[/cut]--
(Continue reading)

Permalink | Reply | 106 comments |
headers
Stephen Collins | 2 May 2004 03:50

Menus borked

I've just done a dist-upgrade using Synaptic.  My apt.conf, etc are 
based off Axel's atrpms.  The whole thing has gone through and performed 
updates on several packages, one of which has destroyed my Gnome menus.  
I'm not 100 per cent sure what was upgraded as I didn't write it down.  
Is there somewhere I can look for a log so I can roll back?

Steve

--

-- 
Em: trib <at> stephencollins.org
Wb: http://www.stephencollins.org
IM: ICQ - 1014940
Permalink | Reply | 4 comments |
headers
Jon Roland | 2 May 2004 04:13

File mysql.sock missing

Tried to launch mysql by executing

# mysql

and got error

ERROR 2002: Can't connect to local MySQL sever through socket 
'/var/lib/mysql/mysql.sock' (2)

I confirmed that the socket was set to that in /etc/my.cnf but doing a

# find / -name mysql.sock

did not find it anywhere on the system. I have checked other mysql files 
and most of the ones I am familiar with seem to be in their proper places.

Mysql was running a few weeks ago, so I have to suspect that, since the 
main way I update my system is with yum update from freshrpms.net, one 
of the rpms might have deleted it. Has anyone else experienced the same 
problem? If so, can anyone suggest a solution? Is this the result of a 
bug in one of the rpms?

-- Jon

----------------------------------------------------------------
Starflight Corporation    7793 Burnet Road #37, Austin, TX 78757
512/374-9585 www.the-spa.com/jon.roland/  jon.roland <at> the-spa.com
Get your free digital certificate from http://www.thawte.com
----------------------------------------------------------------
(Continue reading)

Permalink | Reply | 4 comments |
headers
Edward Rudd | 2 May 2004 05:02

Re: File mysql.sock missing

mysql.sock is created by mysqld when it starts.. it's not part of the
RPM package.. Sot his is NOT a problem with an rpm 
try connecting to your database using the mysql client program

> mysql -u root -p -h databasehost
Enter password:
mysql>

And type this query in..
SHOW VARIABLES LIKE 'socket';
and press enter..
Mysql will then return the location of the socket..  make sure that is
the correct location..
You can also try restarting your mysqld to see if it will re-create the
socket if that is the correct location.

On Sat, 2004-05-01 at 21:13, Jon Roland wrote:
> Tried to launch mysql by executing
> 
> # mysql
> 
> and got error
> 
> ERROR 2002: Can't connect to local MySQL sever through socket 
> '/var/lib/mysql/mysql.sock' (2)
> 
> I confirmed that the socket was set to that in /etc/my.cnf but doing a
> 
> # find / -name mysql.sock
>
(Continue reading)

Permalink | Reply | 2 comments |
headers
William Hooper | 2 May 2004 05:09
Picon
Favicon

Re: File mysql.sock missing


Jon Roland said:
> Tried to launch mysql by executing
>
> # mysql
>
> and got error
>
> ERROR 2002: Can't connect to local MySQL sever through socket
> '/var/lib/mysql/mysql.sock' (2)

What does "/sbin/service mysqld status" say?

--

-- 
William Hooper
Permalink | Reply | 0 comments |
headers
Jon Roland | 2 May 2004 06:15

Re: File mysql.sock missing

Edward Rudd wrote:
> try connecting to your database using the mysql client program
> 
>>mysql -u root -p -h localhost
> Enter password: [mysql]
> mysql>

The above doesn't work to restart the mysqld daemon. Just get the same 
error I reported. What does work is to start the daemon with

# /etc/rc.d/init.d/mysqld start

That created mysql.sock and other files and now I can start a client 
session with the mysql command [options]

Now to figure out why the daemon isn't getting started automatically, 
and what happened to the files created in the last session where it was 
working.

If only I was getting paid for having all this fun. :)

--Jon

----------------------------------------------------------------
Starflight Corporation    7793 Burnet Road #37, Austin, TX 78757
512/374-9585 www.the-spa.com/jon.roland/  jon.roland <at> the-spa.com
Get your free digital certificate from http://www.thawte.com
----------------------------------------------------------------
(Continue reading)

Permalink | Reply | 1 comment |
headers
Edward Rudd | 2 May 2004 07:01

Re: File mysql.sock missing

On Sat, 2004-05-01 at 23:15, Jon Roland wrote:
> Edward Rudd wrote:
> > try connecting to your database using the mysql client program
> > 
> >>mysql -u root -p -h localhost
> > Enter password: [mysql]
> > mysql>
> 
> The above doesn't work to restart the mysqld daemon. Just get the same 
> error I reported. What does work is to start the daemon with
> 
The above wasn't to start the daemon, but to connect to it and retrieve
the running configuration.
> # /etc/rc.d/init.d/mysqld start
> 
> That created mysql.sock and other files and now I can start a client 
> session with the mysql command [options]
> 
> Now to figure out why the daemon isn't getting started automatically, 
> and what happened to the files created in the last session where it was 
> working.
> 
run 
chkconfig --list mysqld
That will list what runlevels mysqld is supposed to start for.
If they are all set to no. (or mainly 3 4 and 5).. then run this
chkconfig mysqld on
If it returns that it is not registered.. run
chkconfig --add mysqld
chkconfig mysqld on
(Continue reading)

Permalink | Reply | 0 comments |

Gmane