Dovecot and mailbox eating
by Alan Cox
Our current dovecot is 0.99.10.4
The author writes:
| Released 0.99.10.5 version. Most importantly fixes mbox corruption in
| certain situations, hopefully it was the only one. Fixes other non-mbox
| problems as well, so this is a recommended upgrade. Only new feature is
| MySQL authentication.
is anyone looking at/packaging .5 given .4 corrupts mailboxes ?
19 years, 11 months
samba 3.0.3-5 bug...?
by MG
Hi!
I think the samba 3.0.3-5 has a bug in FC2. The simple share cannot work.
My smb.conf:
# ------------------------------
[global]
username map = /etc/samba/smbusers
server string = SAMBA host
password server = None
security = share
workgroup = group
client code page = 852
character set = ISO8859-2
hosts allow = 192.168.21.
public = yes
browseable = yes
[Install]
comment = Install
path = /mnt/hda4/Install
public = yes
browseable = yes
# ------------------------------
The win9x clients cannot browse the "Install" share, because samba asks the
password. Why? :O
It write nobody user and password the smbpasswd file. If I remove the nobody
entry from smbpasswd, then after next start samba write it back in smbpasswd.
In FC1 it was not problem. :(
Why does samba ask the password while the share is public(!)??
Bye!
Gabor
19 years, 11 months
samba-3.0.4-1.FC1 update printing bug
by Aurelien Bompard
Hi all
The new version from FC1 updates broke the printing system on my PDC.
I use the following setting :
print command = /usr/bin/lpr -P %p -o raw %s
With drivers on the clients. With the update, the printer was just spitting
raw Postscript characters. Reverting to samba-3.0.0-15 fixed it.
The printer is an HP Laserjet 4100M.
If you need any more info, I'd be glad to help.
Aurélien
--
http://gauret.free.fr ~~~~ Jabber : gauret(a)amessage.info
"Penser est facile, agir est difficile, mais agir selon sa pensée est ce
qu'il y a au monde de plus difficile" -- Leonard de Vinci
19 years, 11 months
CPAN spec file generator needs testing, feedback
by Steven Pritchard
I've mentioned here before that I've written a script to build
"correct" (in other words, "will pass QA") spec files for perl
modules. Thanks to José Pedro Oliveira, the output of the script is
now *very* close to the "official" fedora.us spec template.
The script seems useful enough that I'd really like some more feedback
on it. It can be found here:
http://www.silug.org/~steve/software/scripts/perl/cpanspec
Besides trying to be correct, the script *tries* to automatically
determine BuildRequires, BuildArch, package description, and which
files are documentation. The generated spec files *will* have to be
edited, but hopefully only slightly.
Some notes:
* Since there doesn't seem to be a way to guess the license, the
script now uses the string "CHECK(GPL or Artistic)" so that
rpmlint will complain and remind the packager/reviewer to actually
verify the license.
* The template includes
BuildRequires: perl >= 1:5.6.1
I've left that out because I see any reason to clutter up
fedora.us packages with cruft for unsupported releases. If anyone
feels strongly that I'm wrong here, please let me know why.
* The template includes
chmod -R u+w $RPM_BUILD_ROOT/*
I've gone a step further and made that "u+rwX,go+rX,go-w". IMHO,
if we're going to touch each file, we may as well *really* touch
each file. ;-) Again, if anyone thinks I'm wrong, please tell me
why...
* The description is reformatted using Text::Autoformat. If you
want to test the script, perhaps this would be a good excuse to QA
my perl-Text-Autoformat package. :-)
https://bugzilla.fedora.us/show_bug.cgi?id=1354
Otherwise, you can comment out a couple of lines (the "use" line
and the one that calls autoformat()).
Steve
--
Steven Pritchard - K&S Pritchard Enterprises, Inc.
Email: steve(a)kspei.com http://www.kspei.com/
Phone: (618)398-7360 Mobile: (618)567-7320
19 years, 11 months
proposal: best practices for cron jobs in RPM packages
by Florin Andrei
(sorry for the cross-post, but the potential audience for the proposal
is quite large)
(i'll start with a particular case, then develop the issue towards more
general aspects)
I'm looking at the clamav-db-0.72-1.1.fc2.dag package. It's pretty
cleanly built (which is a feature of that entire repository, kudos to
Dag Wieers!), however, my pet peeve with it is the freshclam cron job.
By default, the package relies on the /etc/cron.daily/freshclam script
to perform the update. That means the job is run whenever the cron.daily
job is set to.
FC2 by default sets cron.daily to run at 04:02 AM every day.
Due to timezone dispersion, the clamav-db users of Dag's repository will
run that cron job pretty much around the clock, but still all of them
will run it at XX:02 - two minutes after :00 each hour. Yet still
probably most of them are in timezone bunches: Northern America (3
timezones), Europe (about 2), parts of Asia (2...3 timezones) so the
timezone dispersion is perhaps not as even as it seems.
This will create artificial spikes on the ClamAV servers, making it more
difficult for the ClamAV team to continue to provide the free service to
the community.
The problem is yet more alleviated somehow by the fact that
database.clamav.net is a distributed database. Still the load spike
problem still remains (it's just not as big).
The solution to it is to spread the load created by all those
.dag.i386.rpm users even further.
However, changing the schedule of a job in /etc/cron.daily cannot be
done by the sysadmin without affecting all other jobs in that directory.
I think i have an improvement.
Why use a file in /etc/cron.daily which has all those disadvantages
(creates load spikes worldwide, it's hard to change) and not just stick
a file in /etc/cron.d ? After all, that's what the FC2 MRTG package
does, and it does it successfully.
It's much easier to change: each file in /etc/cron.d can be adjusted to
its own schedule.
It's a lot more fine-grained: a sysadmin could configure it to run every
hour, every half an hour, every 5 minutes on Fridays 13th or other weird
combinations.
Better yet, the %postinstall RPM macro could go ahead and fill up upon
install a random 0...59 value for the minutes field and a random 0...23
value for the hour field, this way making things a lot easier for the
ClamAV database servers.
In fact, /etc/cron.d seems to be the ideal spot to stick cron jobs for
RPM packages. There are very few applications that need cron jobs to be
run exactly once a day/week/month in every conceivable situation, and
most of those are actually within tightly interlocked sequences such as:
run logwatch/webalizer first, then anacron, then finally logrotate.
So, what i'm saying is, perhaps the authors of custom RPM packages (and
even the non-custom ones, the ones included with the distribution)
should use more aggresively /etc/cron.d to run the cron jobs for their
packages.
You get more flexibility, ease of administration, more intelligent
behaviour of the system overall (see the automatic randomization of the
schedule after installing the package).
/etc/cron.daily confines the packages to quite tight limits; sometimes
that's good (see above mention about cron sequences) but i believe it's
usually not optimal.
Sure, the sysadmin can change everything in a package, including the
ways cron jobs are set. But, as i painfully noticed after upgrading my
home server to FC2, the more you deviate from the trodden path, the more
work you end up doing.
Note: I believe (but i'm not sure) that crond must be notified after
adding/removing a file to/from /etc/cron.d - if that's true, then any
package adding/removing a script to/from /etc/cron.d should do a
"service cron reload" in the %postinstall and %postun macros. That's not
hard and it's actually an elegant solution.
--
Florin Andrei
http://florin.myip.org/
19 years, 11 months
rawhide report: 20040608 changes
by Build System
Updated Packages:
ash-0.3.8-19
------------
* Mon Jun 07 2004 Lon Hohberger <lhh(a)redhat.com> 0.3.8-19
- Remove alpha-specific hacks; no longer necessary + cause
builds to break.
cyrus-sasl-2.1.18-4
-------------------
* Mon Jun 07 2004 Nalin Dahyabhai <nalin(a)redhat.com> 2.1.18-4
- enable sql auxprop support in a subpackage
- include LDAP_SASLAUTHD documentation file (#124830)
* Fri Jun 04 2004 Nalin Dahyabhai <nalin(a)redhat.com>
- turn on ntlm
devlabel-0.48.03-1
------------------
dietlibc-0.25-2
---------------
* Mon Jun 07 2004 Jeremy Katz <katzj(a)redhat.com> - 0.25-2
- use old qsort implementation, it was faster for our purposes
* Wed May 26 2004 Jeremy Katz <katzj(a)redhat.com> - 0.25-1
- update to 0.25
krb5-1.3.3-8
------------
* Mon Jun 07 2004 Nalin Dahyabhai <nalin(a)redhat.com> 1.3.3-8
- rebuild
* Fri Jun 04 2004 Nalin Dahyabhai <nalin(a)redhat.com> 1.3.3-7
- rebuild
* Fri Jun 04 2004 Nalin Dahyabhai <nalin(a)redhat.com> 1.3.3-6
- apply updated patch from MITKRB5-SA-2004-001 (revision 2004-06-02)
nss_ldap-220-1
--------------
* Mon Jun 07 2004 Nalin Dahyabhai <nalin(a)redhat.com> 220-1
- update to 220, pam_ldap 169
* Thu Apr 15 2004 Nalin Dahyabhai <nalin(a)redhat.com>
- fail at build-time if the modules produced can't be loaded
- fix missing module in pam_ldap build
openssh-3.8.1p1-1
-----------------
* Mon Jun 07 2004 Nalin Dahyabhai <nalin(a)redhat.com> 3.8.1p1-1
- request gssapi-with-mic by default but not delegation (flag day for anyone
who used previous gssapi patches)
- no longer request x11 forwarding by default
openssl-0.9.7a-37
-----------------
* Mon Jun 07 2004 Nalin Dahyabhai <nalin(a)redhat.com> 0.9.7a-37
- build for linux-alpha-gcc instead of alpha-gcc on alpha (Jeff Garzik)
rpmdb-fedora-2-0.20040608
-------------------------
selinux-policy-strict-1.13.4-2
------------------------------
* Mon Jun 07 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.4-2
- Add most of Russell's mods
* Mon Jun 07 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.4-1
- Handle newrole changes for new design
- Update to latest from NSA
selinux-policy-targeted-1.13.4-2
--------------------------------
* Mon Jun 07 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.4-2
- Apply allot of Russell's mods
* Mon Jun 07 2004 Dan Walsh <dwalsh(a)redhat.com> 1.13.4-1
- Handle newrole changes for new design
- Update to latest from NSA
subversion-1.0.4-1
------------------
* Sat May 22 2004 Joe Orton <jorton(a)redhat.com> 1.0.4-1
- update to 1.0.4
* Fri May 21 2004 Joe Orton <jorton(a)redhat.com> 1.0.3-2
- build /usr/bin/* as PIEs
- add fix for libsvn_client symbol namespace violation (r9608)
* Wed May 19 2004 Joe Orton <jorton(a)redhat.com> 1.0.3-1
- update to 1.0.3
19 years, 11 months
Multiple LUN support?
by Hugh Caley
Is Fedora still distributed without multiple LUN support by default? If
so, I wonder what the advantage is to that?
Hugh
--
Hugh Caley | Unix Systems Administrator | CIS
AFFYMETRIX, INC. | 6550 Vallejo St. Ste 100 | Emeryville, CA 94608
Tel: 510-428-8537 | Hugh_Caley(a)affymetrix.com
19 years, 11 months
syslog snafu
by Richard Hally
What has happened to syslog? below is the tail of /var/log/messages.
This is with kernel-2.6.6-1.422 and everything updated to the current
/devel. I have tried both enforcing and permissive modes and rebooted,
relabeled and still do not get anything but the date-time and
hostname. It's somewhat difficult to work on SELinux without messages!
Thanks for any help,
Richard Hally
Jun 8 23:51:49 new2 ntpd[2486]: synchronized to 209.132.176.4, stratum=1
Jun 8 23:59:21 new2 ntpd[2486]: kernel time sync disabled 0041
Jun 9 00:02:34 new2 ntpd[2486]: kernel time sync enabled 0001
Jun 9 02:16:46 new2 su(pam_unix)[3648]: session closed for user root
Jun 9 03:44:41 new2 su(pam_unix)[3909]: session opened for user root by
richard(uid=500)
Jun 9 15:00:22 new2 kernel: Kernel logging (proc) stopped.
Jun 9 15:00:22 new2 kernel: Kernel log daemon terminating.
Jun 9 15:00:24 new2 syslog: klogd shutdown succeeded
Jun 9 15:00:24 new2 exiting on signal 15
Jun 9 15:00:25 new2 syslogd 1.4.1: restart.
Jun 9 15:00:25 new2
Jun 9 15:00:25 new2 last message repeated 2 times
Jun 9 15:00:27 new2
Jun 10 03:16:10 new2
Jun 10 03:19:38 new2 last message repeated 20 times
Jun 10 03:31:56 new2 last message repeated 2 times
Jun 10 03:33:38 new2 last message repeated 11 times
Jun 10 03:36:13 new2
Jun 10 03:36:14 new2 last message repeated 2 times
Jun 10 03:36:14 new2 exiting on signal 15
Jun 10 03:36:14 new2 syslogd 1.4.1: restart.
Jun 10 03:36:14 new2
Jun 10 03:36:14 new2 last message repeated 2 times
Jun 10 03:36:17 new2
Jun 10 03:37:12 new2
Jun 10 03:40:08 new2 last message repeated 30 times
Jun 10 03:40:45 new2 last message repeated 9 times
Jun 10 03:40:46 new2
Jun 10 03:40:46 new2
Jun 10 03:40:54 new2 last message repeated 21 times
Jun 10 03:40:54 new2
Jun 10 03:40:54 new2
Jun 10 03:40:54 new2
Jun 10 03:40:58 new2 last message repeated 17 times
Jun 10 03:40:58 new2 exiting on signal 15
Jun 10 03:42:31 new2 syslogd 1.4.1: restart.
Jun 10 03:42:31 new2
Jun 10 03:42:33 new2 last message repeated 331 times
Jun 10 03:42:33 new2
Jun 10 03:42:33 new2
Jun 10 03:42:33 new2
Jun 10 03:42:33 new2 last message repeated 7 times
Jun 10 03:42:33 new2
Jun 10 03:42:33 new2
Jun 10 03:42:33 new2
Jun 10 03:43:16 new2 last message repeated 194 times
Jun 10 03:46:58 new2 last message repeated 13 times
Jun 10 03:49:32 new2 last message repeated 2 times
Jun 10 03:49:33 new2 last message repeated 2 times
Jun 10 03:49:33 new2
Jun 10 03:49:33 new2
Jun 10 03:50:12 new2 last message repeated 11 times
Jun 10 03:50:50 new2 last message repeated 31 times
Jun 10 03:50:50 new2
Jun 10 03:50:50 new2
Jun 10 03:50:51 new2 last message repeated 6 times
Jun 10 03:50:51 new2
Jun 10 03:50:51 new2
Jun 10 03:50:51 new2
Jun 10 03:50:54 new2 last message repeated 17 times
Jun 10 03:50:54 new2 exiting on signal 15
Jun 10 04:03:27 new2 syslogd 1.4.1: restart.
Jun 10 04:03:27 new2
Jun 10 04:03:28 new2 last message repeated 308 times
Jun 10 04:03:28 new2
Jun 10 04:03:28 new2
Jun 10 04:03:28 new2
Jun 10 04:03:28 new2 last message repeated 6 times
Jun 10 04:03:28 new2
Jun 10 04:03:28 new2
Jun 10 04:03:29 new2
Jun 10 04:03:29 new2
Jun 10 04:03:30 new2
Jun 10 04:04:15 new2 last message repeated 175 times
Jun 10 04:07:53 new2 last message repeated 15 times
Jun 10 04:10:49 new2
Jun 10 04:11:11 new2 last message repeated 9 times
Jun 10 04:11:11 new2
Jun 10 04:11:11 new2
Jun 10 04:11:12 new2 last message repeated 6 times
Jun 10 04:11:12 new2
Jun 10 04:11:12 new2
Jun 10 04:11:12 new2
Jun 10 04:11:15 new2 last message repeated 17 times
Jun 10 04:11:15 new2 exiting on signal 15
Jun 10 04:12:41 new2 syslogd 1.4.1: restart.
Jun 10 04:12:41 new2
Jun 10 04:12:41 new2 last message repeated 245 times
Jun 10 04:12:42 new2
Jun 10 04:12:42 new2 last message repeated 5 times
Jun 10 04:12:42 new2
Jun 10 04:12:43 new2 last message repeated 5 times
Jun 10 04:12:43 new2
Jun 10 04:12:43 new2
Jun 10 04:12:43 new2
Jun 10 04:12:43 new2 last message repeated 6 times
Jun 10 04:12:43 new2
Jun 10 04:13:29 new2 last message repeated 94 times
Jun 10 04:13:37 new2 last message repeated 8 times
Jun 10 04:13:37 new2
Jun 10 04:13:38 new2
Jun 10 04:13:46 new2 last message repeated 12 times
Jun 10 04:13:55 new2
Jun 10 04:14:17 new2
Jun 10 04:17:10 new2
[root@new2 log]#
19 years, 11 months
xorg and IBM Thinkpad T30
by Hetz Ben Hamo
Hi,
I'm using FC2 with IBM Thinkpad T30, and so far it works great with xorg
version of X11.
However, when I'm using the docking port and booting the T30 without opening
it, I get a 640x480 resolution on my CRT, no matter how much I fiddle with
xorg.conf..
Anyone on the list had this problem? it only happends when the machine is
closed and powered from the docking port...
Thanks,
Hetz
19 years, 11 months
