From mikkel at t48.dk Fri Jan 6 09:58:30 2006 From: mikkel at t48.dk (Mikkel Nielsen) Date: Fri, 06 Jan 2006 10:58:30 +0100 Subject: [classic-discuss] Syslog/logrotate In-Reply-To: <20051204210101.GA2682@ws64.jh.dy.fi> References: <4392FF02.2060802@t48.dk> <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> Message-ID: <43BE3F46.9030403@t48.dk> Their seems to be a bug in the logrotate script or syslog behaviour. The default for the syslog server is to run as the user syslog From the man file: Note that when this option is in use, syslogd will open all log files as root when the daemon is first started; however, after a SIGHUP the files will be reopened as the non-privileged user. You should take this into account when deciding the ownership of the log files. So logrotate needs to create all files as the syslog user. man for logrotate states that all files will keep their owner ship. But syslog creates new files as root. In order to compensate for this logrotate should use: create 0600 syslog syslog or syslog deamon restart should include a chown syslog.syslog in a start/restart -- Mikkel From mbak at fxnet.hu Fri Jan 6 10:23:53 2006 From: mbak at fxnet.hu (Mikael Bak) Date: Fri, 06 Jan 2006 11:23:53 +0100 Subject: [classic-discuss] tcs and xen? Message-ID: <1136543032.3407.12.camel@localhost.localdomain> Hi list, I would like to know if anyone here have tried to apply the xen patches to the kernel and perhaps build the xen userland tools as tcs rpm package? I ask before start building to avoid reinventing wheels :-) TIA, Mikael From jh at tinysofa.org Fri Jan 6 11:13:46 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Fri, 6 Jan 2006 13:13:46 +0200 Subject: [classic-discuss] Syslog/logrotate In-Reply-To: <43BE3F46.9030403@t48.dk> References: <4392FF02.2060802@t48.dk> <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> <43BE3F46.9030403@t48.dk> Message-ID: <20060106111346.GA1136@ws64.jh.dy.fi> Hi, On 2006-01-06, Mikkel Nielsen wrote: > Their seems to be a bug in the logrotate script or syslog behaviour. > > So logrotate needs to create all files as the syslog user. > man for logrotate states that all files will keep their owner ship. But > syslog creates new files as root. This shouldn't be a problem with default configuration since default logfiles are created with syslog ownership. When logrotate rotates logfiles it keeps the ownership for new files. Am I correct? However I can see that a problem occurs if you define a custom syslog log file (in /etc/syslog.conf) and you don't create an initial log file manually with syslog ownership. Now when syslog creates the log file first time it ends up to be owned by root. > In order to compensate for this logrotate should use: > create 0600 syslog syslog This is not a correct fix since user may not use logrotate for custom log files. > or syslog deamon restart should include a chown syslog.syslog in a > start/restart Yes, it sound correct that syslogd should create new logfiles with syslog ownership rather than root. Did I understand the problem correctly? Also could you explain the circumstances where you saw the problem in more detail? -- Jaakko From jh at tinysofa.org Fri Jan 6 19:03:19 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Fri, 6 Jan 2006 21:03:19 +0200 Subject: [classic-discuss] Syslog/logrotate In-Reply-To: <43BE58B8.6070905@t48.dk> References: <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> <43BE3F46.9030403@t48.dk> <20060106111346.GA1136@ws64.jh.dy.fi> <43BE58B8.6070905@t48.dk> Message-ID: <20060106190319.GA2132@ws64.jh.dy.fi> [I got a confirmation from Mikkel that it was as I thought.] Strictly taken it's not a bug but a documented behavior. However it's indeed annoying. Some possible fixes for the problem: 1) Patch syslogd to drop root privileges before file creation. The problem is that /var/log directory permissions must be changed to allow writing for syslog user. (One could also patch the syslogd to chown file before dropping the privileges. However this patch would become more complex.) Also maybe there are some other reasons why it was implemened this way originally. 2) Add a comment to default /etc/syslog.conf that states that the log files should be owned by syslog. 3) Run syslogd as root. Doesn't sound good. -- Jaakko From mbak at fxnet.hu Tue Jan 10 09:26:16 2006 From: mbak at fxnet.hu (Mikael Bak) Date: Tue, 10 Jan 2006 10:26:16 +0100 Subject: [classic-discuss] clamav 0.88 for tcs1.1 and 2.0 Message-ID: <1136885175.3384.3.camel@localhost.localdomain> Hi list, Yes, I know tcs1.1 is history, but I still haven't got around to update all machines yet. In case someone else needs this package I made it avaiable here: http://miba.fxnet.hu/tinysofa/ And I made one for tcs2.0 too in case someone wants it before it makes it into contrib. Cheers, Mikael From jh at tinysofa.org Thu Jan 12 05:27:44 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Thu, 12 Jan 2006 07:27:44 +0200 Subject: [classic-discuss] tinysofa classic server 2.0 Update 3 Message-ID: <20060112052743.GA1130@ws64.jh.dy.fi> tinysofa classic server 2.0 Update 3 (Ceara) is now generally available. This release focuses on bug fixes, integrates all released security fixes, and updates various packages to the more recent upstream releases. Highlights: * openswan 2.4.4 * samba 3.0.20b * smart 0.41 * vim 6.4 * drbd 0.7.14 ChangeLog: http://classic.tinysofa.org/documentation/index.cgi?TwoPointZeroChanges tinysofa classic server may be downloaded from: http://classic.tinysofa.org/download/ 2.0 users can upgrade to update 3 with apt: apt-get mirror-select (not needed if sources are already configured) apt-get update apt-get dist-upgrade or possibly with smart: smart-mirror-select (not needed if sources are already configured) smart update smart upgrade -- Jaakko From jh at tinysofa.org Thu Jan 12 16:44:56 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Thu, 12 Jan 2006 18:44:56 +0200 Subject: [classic-discuss] Syslog/logrotate In-Reply-To: <43BE3F46.9030403@t48.dk> References: <4392FF02.2060802@t48.dk> <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> <43BE3F46.9030403@t48.dk> Message-ID: <20060112164455.GA1856@ws64.jh.dy.fi> Hi, On 2006-01-06, Mikkel Nielsen wrote: > or syslog deamon restart should include a chown syslog.syslog in a > start/restart I patched syslogd to chown log files that it creates. (to the user specified with the -u switch) This makes it to work as expected in most cases. However there are still possible scenarios where it doesn't behave nicely. (eg. with pipes) "Fixing" those would require rewriting the syslogd initialization routine. I think that it works now well enough for most of the users and the behaviour is documented on the manual page. I have compiled new packages for testing: http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.i586.rpm http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.src.rpm Testing is appreciated. -- Jaakko From mikkel at t48.dk Thu Jan 12 16:54:13 2006 From: mikkel at t48.dk (Mikkel Nielsen) Date: Thu, 12 Jan 2006 17:54:13 +0100 Subject: [classic-discuss] Syslog/logrotate In-Reply-To: <20060112164455.GA1856@ws64.jh.dy.fi> References: <4392FF02.2060802@t48.dk> <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> <43BE3F46.9030403@t48.dk> <20060112164455.GA1856@ws64.jh.dy.fi> Message-ID: <43C689B5.9050508@t48.dk> Hi, I will start testing right away. Thanks for now! -- Mikkel Jaakko Heinonen wrote: > Hi, > > On 2006-01-06, Mikkel Nielsen wrote: > >>or syslog deamon restart should include a chown syslog.syslog in a >>start/restart > > > I patched syslogd to chown log files that it creates. (to the user > specified with the -u switch) This makes it to work as expected in most > cases. However there are still possible scenarios where it doesn't > behave nicely. (eg. with pipes) "Fixing" those would require rewriting > the syslogd initialization routine. I think that it works now well > enough for most of the users and the behaviour is documented on the > manual page. > > I have compiled new packages for testing: > > http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.i586.rpm > http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.src.rpm > > Testing is appreciated. > From mikkel at t48.dk Wed Jan 18 13:50:33 2006 From: mikkel at t48.dk (Mikkel R. Nielsen) Date: Wed, 18 Jan 2006 14:50:33 +0100 Subject: [classic-discuss] Syslog/logrotate and ESX question In-Reply-To: <43C689B5.9050508@t48.dk> References: <4392FF02.2060802@t48.dk> <43930135.5090200@tinysofa.org> <43930C79.3090206@t48.dk> <20051204173601.GA2130@ws64.jh.dy.fi> <43932FBB.1090906@t48.dk> <20051204195410.GA1116@ws64.jh.dy.fi> <43934B77.5090705@t48.dk> <20051204210101.GA2682@ws64.jh.dy.fi> <43BE3F46.9030403@t48.dk> <20060112164455.GA1856@ws64.jh.dy.fi> <43C689B5.9050508@t48.dk> Message-ID: <43CE47A9.5050005@t48.dk> Hi, We have tested for almost a week now and everything works fine, thanks! *Another question* Has anyone got the ESX tool's to work on the 2.6 krenel?? -- Mikkel Mikkel Nielsen wrote: > Hi, > > > I will start testing right away. > > Thanks for now! > > -- > Mikkel > > Jaakko Heinonen wrote: > >> Hi, >> >> On 2006-01-06, Mikkel Nielsen wrote: >> >>> or syslog deamon restart should include a chown syslog.syslog in a >>> start/restart >> >> >> >> I patched syslogd to chown log files that it creates. (to the user >> specified with the -u switch) This makes it to work as expected in most >> cases. However there are still possible scenarios where it doesn't >> behave nicely. (eg. with pipes) "Fixing" those would require rewriting >> the syslogd initialization routine. I think that it works now well >> enough for most of the users and the behaviour is documented on the >> manual page. >> >> I have compiled new packages for testing: >> >> http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.i586.rpm >> http://jh.dy.fi/~jaakko/sysklogd/sysklogd-1.4.1-41jh.src.rpm >> >> Testing is appreciated. >> > > _______________________________________________ > classic-discuss mailing list > classic-discuss at tinysofa.org > http://lists.tinysofa.org/mailman/listinfo/classic-discuss From mikael at tinysofa.org Thu Jan 26 13:05:01 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Thu, 26 Jan 2006 14:05:01 +0100 Subject: [classic-discuss] MyDNS anyone? Message-ID: <1138280700.3383.103.camel@localhost.localdomain> hi list, I have been looking for a replacement for bind. When I started using bind I had like three or four domains to administer. Then it's no big deal to have them all in one text file. But now when I have almost 100 of them, it seems more obivious to use an sql database backend or perhaps at least ldap backend for the DNS data storage. I know there are patches for bind I could use, but they all seemed outdated or still under development or whatever. Then I found MyDNS[1]. This one seem to solve my problems, but the software isn't very nice to rpm packagers :-) Nevermind. I just wanted to hear from the list if anyone of you have heard of this software. If it's reliable, and if it's worth putting in contrib. I will probably use it in production after some extensive testing. I'm sick and tired of bind's config files :-) Cheers, Mikael [1] http://mydns.bboy.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.tinysofa.org/pipermail/classic-discuss/attachments/20060126/b270cc23/attachment.bin From mikkel at t48.dk Thu Jan 26 14:21:53 2006 From: mikkel at t48.dk (Mikkel R. Nielsen) Date: Thu, 26 Jan 2006 15:21:53 +0100 Subject: [classic-discuss] MyDNS anyone? In-Reply-To: <1138280700.3383.103.camel@localhost.localdomain> References: <1138280700.3383.103.camel@localhost.localdomain> Message-ID: <43D8DB01.4000707@t48.dk> Hi. We are using MyDNS on a TSC 2.0 installed from source and its running fine... If you need any config files just say so! -- Mikkel Mikael Bak wrote: > hi list, > > I have been looking for a replacement for bind. > > When I started using bind I had like three or four domains to > administer. Then it's no big deal to have them all in one text file. But > now when I have almost 100 of them, it seems more obivious to use an sql > database backend or perhaps at least ldap backend for the DNS data > storage. > > I know there are patches for bind I could use, but they all seemed > outdated or still under development or whatever. > > Then I found MyDNS[1]. This one seem to solve my problems, but the > software isn't very nice to rpm packagers :-) Nevermind. I just wanted > to hear from the list if anyone of you have heard of this software. If > it's reliable, and if it's worth putting in contrib. I will probably use > it in production after some extensive testing. I'm sick and tired of > bind's config files :-) > > Cheers, > Mikael > > [1] http://mydns.bboy.net/ > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > classic-discuss mailing list > classic-discuss at tinysofa.org > http://lists.tinysofa.org/mailman/listinfo/classic-discuss From mikkel at t48.dk Sat Jan 28 22:35:44 2006 From: mikkel at t48.dk (Mikkel R. Nielsen) Date: Sat, 28 Jan 2006 23:35:44 +0100 Subject: [classic-discuss] Logitech WebCam In-Reply-To: <1138280700.3383.103.camel@localhost.localdomain> References: <1138280700.3383.103.camel@localhost.localdomain> Message-ID: <43DBF1C0.9080604@t48.dk> Hi. Has anyone got a Logitech QuickCam running under TSC kernel 2.6.13-4ts. -- Mikkel From mikael at tinysofa.org Tue Jan 31 18:38:18 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Tue, 31 Jan 2006 19:38:18 +0100 Subject: [classic-discuss] ANN: MyDNS testing package for TCS Message-ID: <1138732698.5649.10.camel@localhost.localdomain> Hi list, For anyone interested in MyDNS there's now a "testing" rpm package. Avaiable for download here: http://miba.fxnet.hu/tinysofa/tcs2.0/test/ Happy testing! Mikael -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.tinysofa.org/pipermail/classic-discuss/attachments/20060131/eaec94be/attachment.bin