On Tuesday 13 August 2019 15:03:53 Lee wrote:
> On 8/13/19, Gene Heskett wrote:
> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> >> Gene Heskett wrote:
> >> > Its good that we can fix it, BUT IF you are going to restrict
> >> > where we keep logfiles like this then FIX the /var/log perms
On Tuesday 13 August 2019 15:03:53 Lee wrote:
> On 8/13/19, Gene Heskett wrote:
> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> >> Gene Heskett wrote:
> >> > Its good that we can fix it, BUT IF you are going to restrict
> >> > where we keep logfiles like this then FIX the /var/log perms
On 8/13/19, Gene Heskett wrote:
> On Tuesday 13 August 2019 02:24:34 deloptes wrote:
>
>> Gene Heskett wrote:
>> > Its good that we can fix it, BUT IF you are going to restrict where
>> > we keep logfiles like this then FIX the /var/log perms so that
>> > fetchmail, procmail, spamassassin, clamav
On Tuesday 13 August 2019 13:06:23 Dan Purgert wrote:
> Gene Heskett wrote:
> > On Tuesday 13 August 2019 05:41:52 Dan Purgert wrote:
> >> Gene Heskett wrote:
> >> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> >> > [...]
> >> >
> >> >> I am not aware of any program I've been using
> >> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> On Tuesday 13 August 2019 05:41:52 Dan Purgert wrote:
>
>> Gene Heskett wrote:
>> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
>> > [...]
>> >
>> >> I am not aware of any program I've been using
>> >> for the past 15y th
On Tuesday 13 August 2019 05:41:52 Dan Purgert wrote:
> Gene Heskett wrote:
> > On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> > [...]
> >
> >> I am not aware of any program I've been using
> >> for the past 15y that would have a problem writing in /var/log
> >
> > Then tell me how fetchmail
On Tue, Aug 13, 2019 at 09:30:34AM +1200, Philip wrote:
> I just updated from Debian 8 to 9 and I'm getting the following error. I'm
> guessing it's something to do with permissions?
>
> Something to do with the create 640 root adm?
>
> /etc/cron.daily/logrotate:
> error: unable to open /home/ph
PS: I do (now) recall that one of the descriptions of how to do what I wanted
was in an old (online) issue of Dr. Dobbs, and I spent a fair amount of time
trying to get that one to do what I wanted, but it refused to cooperate ;-)
On Tuesday, August 13, 2019 07:58:16 AM rhkra...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> [...]
>> I am not aware of any program I've been using
>> for the past 15y that would have a problem writing in /var/log
>
> Then tell me how fetchmail, procmail, clamav or s
On Tuesday 13 August 2019 02:24:34 deloptes wrote:
> Gene Heskett wrote:
> > Its good that we can fix it, BUT IF you are going to restrict where
> > we keep logfiles like this then FIX the /var/log perms so that
> > fetchmail, procmail, spamassassin, clamav and its ilk, running as
> > the user can
On Tuesday 13 August 2019 01:30:09 Erik Christiansen wrote:
> On 13.08.19 00:38, Gene Heskett wrote:
> > Its good that we can fix it, BUT IF you are going to restrict where
> > we keep logfiles like this then FIX the /var/log perms so that
> > fetchmail, procmail, spamassassin, clamav and its ilk,
Gene Heskett wrote:
> Its good that we can fix it, BUT IF you are going to restrict where we
> keep logfiles like this then FIX the /var/log perms so that fetchmail,
> procmail, spamassassin, clamav and its ilk, running as the user can
> access /var/log to keep its logs. Debian's legendary parano
On 13.08.19 00:38, Gene Heskett wrote:
> Its good that we can fix it, BUT IF you are going to restrict where we
> keep logfiles like this then FIX the /var/log perms so that fetchmail,
> procmail, spamassassin, clamav and its ilk, running as the user can
> access /var/log to keep its logs. Debi
On 2019-08-13 00:38 -0400, Gene Heskett wrote:
[rant skipped]
> So just where in tunket _are_ we supposed to be able to keep our logs
> then? A place that Just Works would sure be appreciated.
Putting them under /home is fine, see this comment in
/lib/systemd/system/logrotate.service:
,
| #
On 2019-08-13 06:59 +0300, Teemu Likonen wrote:
> phi...@treads.nz [2019-08-13T09:30:34+12] wrote:
>
>> I just updated from Debian 8 to 9 and I'm getting the following error.
>> I'm guessing it's something to do with permissions?
>>
>> Something to do with the create 640 root adm?
>>
>> /etc/cro
On Monday 12 August 2019 23:59:39 Teemu Likonen wrote:
> phi...@treads.nz [2019-08-13T09:30:34+12] wrote:
> > I just updated from Debian 8 to 9 and I'm getting the following
> > error. I'm guessing it's something to do with permissions?
> >
> > Something to do with the create 640 root adm?
> >
>
phi...@treads.nz [2019-08-13T09:30:34+12] wrote:
> I just updated from Debian 8 to 9 and I'm getting the following error.
> I'm guessing it's something to do with permissions?
>
> Something to do with the create 640 root adm?
>
> /etc/cron.daily/logrotate:
> error: unable to open /home/philip/lo
Afternoon,
I just updated from Debian 8 to 9 and I'm getting the following error.
I'm guessing it's something to do with permissions?
Something to do with the create 640 root adm?
/etc/cron.daily/logrotate:
error: unable to open /home/philip/logs/access.log.1 for compression
error: unable to
18 matches
Mail list logo
