ISISComputingGroup / ISISComputingGroup/IBEX

ProcServ: reproduce issue with "bad"/"locked" permissions

Open
#8,555 4 comments 0 reactions 0 assignees View on GitHub
5 standdown
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Description

# Issue Description

As a developer I would like procserv log files to be reliably created with correct permissions / created with permissions that can't be seen as the file is locked.

On many instruments, particularly (but not exclusively) at the time of starting the IBEX server, the procserv log files can be created with invalid permissions. The symptoms are that:
- Right click -> properties -> permissions is unable to show file permissions correctly
- `dir /q` reports `...` as the file owner rather than an actual username
- The files are not readable by anyone (including admin)

Although this is happening on most instruments, it is _not_ happening on dev or test machines. This ticket is to find a _reliable_ way to reproduce the problem, ideally without an instrument machine, so that we can investigate/fix it.

Although this was noticed in the context of log rotation, it's actually a more general problem as it would prevent us from looking at these log files to diagnose a problem.

### How & Where?

procServ is in `EPICS-tools`.

### Reproducible (Yes/No)?

No: finding a way to reproduce this reliably is part of this issue.

# Acceptance Criteria
- [ ] Documented reliable way to trigger this issue

Either:
- [ ] Issue fixed
or
- [ ] Follow-up issue created & proposed to fix

# How to Review

Check that you can reliably reproduce this issue.

planning 82:00 2024/10/31

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.