From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] pveproxy: create log directory when starting
Date: Wed, 16 Apr 2025 11:21:57 +0200 [thread overview]
Message-ID: <s8o7c3kh33v.fsf@proxmox.com> (raw)
In-Reply-To: <1744791375.g77jk7f9f3.astroid@yuna.none>
Fabian Grünbichler <f.gruenbichler@proxmox.com> writes:
> On April 15, 2025 11:38 am, Maximiliano Sandoval wrote:
>> We only create this directory while installing the package. If a user
>> deletes /var/log then they will lose access to the web UI.
>
> until the reinstall or upgrade the package?
>
>> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
>> ---
>> bin/pveproxy | 18 +++++++++++++++---
>> 1 file changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/bin/pveproxy b/bin/pveproxy
>> index 20e8f2ab2..1090df039 100755
>> --- a/bin/pveproxy
>> +++ b/bin/pveproxy
>> @@ -19,12 +19,24 @@ $SIG{'__WARN__'} = sub {
>> $@ = $err;
>> };
>>
>> +sub chown_to_www_data {
>> + my ($dir) = @_;
>> +
>> + my $gid = getgrnam('www-data') || die "getgrnam failed - $!\n";
>> + my $uid = getpwnam('www-data') || die "getpwnam failed - $!\n";
>> +
>> + chown($uid, $gid, $dir);
>> +}
>
> the thing that only works as root is the chown, not all of this..
>
>> +
>> my $prepare = sub {
>> my $rundir="/var/run/pveproxy";
>> + my $logdir = '/var/log/pveproxy';
>> +
>
> but anyway, it would be much easier to read and have better semantics if
> we switch to
>
> if root {
> my $uid = ..
> my $gid = ..
> mkdir(..)
> chown(..) || warn ...
> mkdir(..)
> chown(..) || warn ...
> }
>
> which has the added benefit of resetting the ownership to the right
> value on reboot/service start, so fixes another potential issue (at the
> cost of two unconditional syscalls).
>
>> if (mkdir($rundir, 0700)) { # only works at first start if we are root)
>> - my $gid = getgrnam('www-data') || die "getgrnam failed - $!\n";
>> - my $uid = getpwnam('www-data') || die "getpwnam failed - $!\n";
>> - chown($uid, $gid, $rundir);
>> + chown_to_www_data($rundir);
>> + }
>> + if (mkdir($logdir, 0700)) {
>> + chown_to_www_data($logdir);
>> }
>> };
>>
>> --
>> 2.39.5
>>
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>
>>
>>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
superseded by https://lore.proxmox.com/pve-devel/20250416091829.124366-1-m.sandoval@proxmox.com/T/#u.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-16 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 9:38 Maximiliano Sandoval
2025-04-16 8:23 ` Fabian Grünbichler
2025-04-16 9:21 ` Maximiliano Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s8o7c3kh33v.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal