This seems to have become a LONG thread, for no
obvious reason.

Look, it's EASY to redirect /var/log to a RAMdisk.
You can do it with cron "@reboot" lines, you can
do it in /etc/init.d, you can do it with systemd.
You just create a RAMdisk and then re-assign
/var/log there with a symlink.

IF you want /var/log to be on a RAMdisk - which
vanishes with every reboot - then it means you
don't CARE what's in /var/log. 99% of the time
that's perfectly viable. /var/log IS useful
for some debugging tasks, but once you've got
it working right, well, who cares ?

In article <gmWdnTMqLKtCSFD5nZ2dnZfqn_WdnZ2d@earthlink.com>,
23k.304 <23k304@bfxw9.net> wrote:
>This seems to have become a LONG thread, for no
>obvious reason.
>
>Look, it's EASY to redirect /var/log to a RAMdisk.
>You can do it with cron "@reboot" lines, you can
>do it in /etc/init.d, you can do it with systemd.
>You just create a RAMdisk and then re-assign
>/var/log there with a symlink.
>
>IF you want /var/log to be on a RAMdisk - which
>vanishes with every reboot - then it means you
>don't CARE what's in /var/log. 99% of the time
>that's perfectly viable. /var/log IS useful
>for some debugging tasks, but once you've got
>it working right, well, who cares ?

In which case, why not re-direct it to /dev/null?

--
Debating creationists on the topic of evolution is rather like trying to
play chess with a pigeon --- it knocks the pieces over, craps on the
board, and flies back to its flock to claim victory.

On 05/08/2023 10:13, Kenny McCormack wrote:
> In article <gmWdnTMqLKtCSFD5nZ2dnZfqn_WdnZ2d@earthlink.com>,
> 23k.304 <23k304@bfxw9.net> wrote:
>> This seems to have become a LONG thread, for no
>> obvious reason.
>>
>> Look, it's EASY to redirect /var/log to a RAMdisk.
>> You can do it with cron "@reboot" lines, you can
>> do it in /etc/init.d, you can do it with systemd.
>> You just create a RAMdisk and then re-assign
>> /var/log there with a symlink.
>>
>> IF you want /var/log to be on a RAMdisk - which
>> vanishes with every reboot - then it means you
>> don't CARE what's in /var/log. 99% of the time
>> that's perfectly viable. /var/log IS useful
>> for some debugging tasks, but once you've got
>> it working right, well, who cares ?
>
> In which case, why not re-direct it to /dev/null?
>
Because it is useful for debugging.
And I am still debugging.

--
"Strange as it seems, no amount of learning can cure stupidity, and
higher education positively fortifies it."

- Stephen Vizinczey

On 8/5/23 5:13 AM, Kenny McCormack wrote:
> In article <gmWdnTMqLKtCSFD5nZ2dnZfqn_WdnZ2d@earthlink.com>,
> 23k.304 <23k304@bfxw9.net> wrote:
>> This seems to have become a LONG thread, for no
>> obvious reason.
>>
>> Look, it's EASY to redirect /var/log to a RAMdisk.
>> You can do it with cron "@reboot" lines, you can
>> do it in /etc/init.d, you can do it with systemd.
>> You just create a RAMdisk and then re-assign
>> /var/log there with a symlink.
>>
>> IF you want /var/log to be on a RAMdisk - which
>> vanishes with every reboot - then it means you
>> don't CARE what's in /var/log. 99% of the time
>> that's perfectly viable. /var/log IS useful
>> for some debugging tasks, but once you've got
>> it working right, well, who cares ?
>
> In which case, why not re-direct it to /dev/null?

I'd considered that, for OPs particular case.

However WHILE the session is running he MIGHT want
to look at something there, maybe. If not, if
never, then /dev/null would be best - nothing
using up space.