similar to: Logrotate problem after start of DST

Hi, I had a C7 virtual machine running on a C7 host for several weeks without any problems. Today I rebootet the host and now the virtual machine does not start anymore. I can see grub coming up and starting the kernel. After some seconds the last thing that is visble on the VM console is "ss perfctr msr (MSR c1 is0)" then the screen goes blank with just a blinking cursor in the upper

What about the update announcements for Centos5? There was nothing posted to centos-announce yet for the updates that have been released so far for Centos5. Also, the centos-announce mailing list options page does not know about Centos5 yet. Best regards, Bernd.

Hi, could it be that the libexif update to 0.6.13-4.0.2 for Centos5 somehow got forgotten? The updates for Centos4 were released nearly two weeks ago. In the meantime also lots of other updates showed up for both Centos4 and Centos5, but still no libexif update for Centos5. Best regards, Bernd.

In case it hasn't been posted before, here's instructions to get the correct time to show up on your Grandstream GXP-2000's: 1. Login to phone 2. Go to Basic Settings tab 3. Change Daylight Savings Time to yes 4. Change Optional Rule to 3,2,7,2,0;11,1,7,2,0;60 (this means change clocks the second sunday of March and back again the first sunday of November - i.e., the new savings

NFS install from a loop-back mounted DVD image fails for me when it actually tries to start the RPM install process. I come to the point where anaconda checks the package dependencies, then it tells that the install process will be started in some minutes and the last thing I see is a message similar to: Preparing transaction from install media. Then this message box disappears and the install

Hi, the latest upstream version of samba rpms for 5.2 is samba-3.0.28-1.el5_2.1. In the Centos 5.2 updates tree there is only samba-3.0.28-0.el5.8 which also is already part of the 5.2 os tree. Could it be that the updates tree just carries the wrong rpms? Best regards, Bernd

Hi, i have several vm's running on KVM hosts. Recently i found out that the time in the log-files of the guests (/var/log/libvirt/qemu/xxx.log) is wrong. The time on the guest itself is right, just the time in the log-files is one hour back. Windows and linux vm's are affected. Also on another host the same. Changing the clock offset does not have any influence, still the wrong time in

I'm noticing that logrotate's default configuration for rotating /var/ log/secure and /var/log/messages partially fails if root's shell is set to /bin/tcsh (via chsh). (Running on CentOS 4.4; logrotate-3.7.1-5.RHEL4). What seems to be happening is that the logrotate.d/syslog postrotate command runs: /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null

FYI, the same bug apears if one mounts the file system using "cifs": -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* Linda W wrote: > Summary: > There appears to be a bug in the "time range" Samba is using on > dates where time is scheduled to "Spring Forward"

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no

Package: logcheck Version: 1.2.41 Problem: Logcheck try to detect if log file have been rotate or not by file size way. Possible attack: - current log file (sizeA) - run logcheck, (logcheck/logtail put inode in offsetfile), offset=sizeA - [attacker run attack 1] - run logrotate - [attacker run attack 2] - run logcheck may don't detect the rotation and don't check the log for attack 1

Hi, a small question.. I'm using NTP to synch our phones with an ntp server, but it seems the Cisco 7912G (with SIP image) does not handle daylight savings time very well? Am I overlooking something or is this a known feature? I'm using GMT+1 and minutes are correct but it doesn't respect DST. SIP software seems to be: v1.02.00(040406A). Cheers, Kristof.

Hi, I needed to logrotate a fil named qmail-queue.log from qmail-scanner. So i've edit /etc/syslog.conf and changed it to: *.info;qmail-queue.none;auth.none;mail.none;authpriv.none;cron.none /var/log/messages (...) # qmail-queue logs qmail-queue /var/spool/qscan/qmail-queue.log Also, i've edit /etc/logrotate.d/syslog and changed to /var/log/messages

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

06.12.2023 10:01, Stefan G. Weichinger via samba: > /var/log/samba/log.rpcd_* { > log.rpcd_spoolss > log.rpcd_spoolss.1 > log.rpcd_spoolss.1.1 > log.rpcd_spoolss.1.1.1 > log.rpcd_spoolss.1.1.1.1 This seems to be a limitation/defect of logrotate itself. At first you had just log.rpcd_spoolss, and at first logrotate run it rotated it to log.rpcd_spoolss.1, - now you have 2 files

Running under Windows XP 64 bit, as.POSIXlt()/as.POSIXct() seem to think that US time zones (EST5EDT, MST7MDT) switched from daylight savings back to standard time on Oct 28, 2007, whereas the switch is actually on Sun Nov 04, 2007. Examples: > Sys.timezone() [1] "Mountain Daylight Time" > as.POSIXct("2007-10-30 12:38:47") [1] "2007-10-30 12:38:47 Mountain

Who is tired of dealing with DST changes? I have asterisk running on FC4, FC4 has been patched and shows the correct MDT timezone and time. Email notifications of voicemail show the message time an hour early (standard time, not daylight). This si the time in the message body, not the email delivery time, so it is coming form asterisk wrong. I did a reload after correcting the

Hi, the last released autofs update for Centos 5 is version autofs-5.0.1-0.rc2.55.el5.1. On 2007-12-20 upstream released version autofs-5.0.1-0.rc2.55.el5.2. As several other updates were released in the meantime maybe the autofs update has been overlooked? Best regards, Bernd.

Hi, the latest Centos 5 krb5 1.6.1-17.el5_1.1 do not get applied to any of my servers. I can see the updates being available on the mirror servers, but "yum update" shows nothing. The krb5 updates for Centos 4 were installed on all of my Centos 4 servers without any problem. Does somebody have any idea what could cause the problem on Centos 5? Thanks in advance, Bernd.

Hi, the C5 updates to openoffice.org-2.0.4-5.4.26 are available on the mirrors, but no announcement has come through the centos-announce mailing list yet. Also, upstream has released gnome-screensaver-2.16.1-5.el5_1.1 and gnome-screensaver-2.16.1-8.el5 (FasTrack channel) beginning of April. Neither is available yet for C5. Best regards, Bernd.