<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op zo 27 aug 2023 om 18:30 schreef Leon Fauster <<a href="mailto:leonfauster@googlemail.com">leonfauster@googlemail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 26.08.23 um 18:41 schrieb Cecil Westerhof:<br>
> Replying on google does not work as I am used to. It sends to the sender <br>
> instead of the group. 😱<br>
> <br>
> Op za 26 aug 2023 om 18:36 schreef Cecil Westerhof <br>
> <<a href="mailto:cldwesterhof@gmail.com" target="_blank">cldwesterhof@gmail.com</a> <mailto:<a href="mailto:cldwesterhof@gmail.com" target="_blank">cldwesterhof@gmail.com</a>>>:<br>
> <br>
> Op za 26 aug 2023 om 14:46 schreef Michael Biebl <<a href="mailto:mbiebl@gmail.com" target="_blank">mbiebl@gmail.com</a><br>
> <mailto:<a href="mailto:mbiebl@gmail.com" target="_blank">mbiebl@gmail.com</a>>>:<br>
> <br>
> Am Sa., 26. Aug. 2023 um 09:44 Uhr schrieb Cecil Westerhof<br>
> <<a href="mailto:cldwesterhof@gmail.com" target="_blank">cldwesterhof@gmail.com</a> <mailto:<a href="mailto:cldwesterhof@gmail.com" target="_blank">cldwesterhof@gmail.com</a>>>:<br>
> ><br>
> > I am at last implementing systemd timers. The service I<br>
> created can have its status queried by a normal user. I thought<br>
> I must have made a mistake. But when I do:<br>
> > systemctl status cron<br>
> ><br>
> > I get:<br>
> > ● cron.service - Regular background program processing daemon<br>
> > Loaded: loaded (/lib/systemd/system/cron.service;<br>
> enabled; preset: enabled)<br>
> > Active: active (running) since Sat 2023-08-19<br>
> 18:12:04 CEST; 6 days ago<br>
> > Docs: man:cron(8)<br>
> > Main PID: 790 (cron)<br>
> > Tasks: 1 (limit: 17837)<br>
> > Memory: 91.0M<br>
> > CPU: 14min 3.110s<br>
> > CGroup: /system.slice/cron.service<br>
> > └─790 /usr/sbin/cron -f<br>
> ><br>
> > Warning: some journal files were not opened due to<br>
> insufficient permissions.<br>
> ><br>
> > Is this the expected behaviour?<br>
> > If not: what could be wrong with my system?<br>
> ><br>
> > This is on Debian 11.<br>
> <br>
> Reading system logs is a privileged operation.<br>
> <br>
> You can grant this privilege to individual users by adding them<br>
> to the<br>
> systemd-journal (or adm) group.<br>
> <br>
> Adding users to the adm will grant them additional privileges,<br>
> so be careful.<br>
> <br>
> <br>
> The user is in the lpadmin group, but not in systemd-journal, or adm<br>
> and still can ask the status.<br>
> Another reply indicates that this is normal.<br>
> <br>
<br>
<br>
Well, you can look at the process list anytime as normal user. So, what <br>
are you trying to accomplishing. Whats the goal? Hiding the process from <br>
the users?<br></blockquote><div><br></div><div style="font-family:courier new,monospace" class="gmail_default">I was surprised that I could see it. And as I understand it, I am certainly not the only one. One reply on my question was even that it is a privileged operation and should not be possible without a group added to the user which was not added to the user.<br></div><div style="font-family:courier new,monospace" class="gmail_default">I agree that you can find out everything with ps, but that is a lot more work.</div><div style="font-family:courier new,monospace" class="gmail_default">I was just surprised that it was possible —and again I am far from the only one—, I just wanted to check it out and now I know it is expected behaviour.</div><div style="font-family:courier new,monospace" class="gmail_default">Better to ask a 'dump' question than staying ignorant I think.<br></div></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Cecil Westerhof</div></div>