Screen returns "Cannot make directory '/run/screen': Permission denied" after a restart of pengwin #763
Comments
|
not sure why some of my test is crossed out? have tried to repast it but just getting worst?? |
|
ok did more research and found this entry https://stackoverflow.com/questions/45517515/running-screen-without-additional-permissions-on-wsl I was using the 'sudo /etc/init.d/screen-cleanup' incorrectly it was to be 'sudo /etc/init.d/screen-cleanup start' although this does fix the issue why do I need to run it when I need to use Screen? is init.d being used? when i execute do I need to install systemd and create a .service file? thank you |
|
Hello @puskyer Thanks for reporting and the detailed explanation. We will investigate if we can do something when the image is being created. Regards, |
|
Thank you |
|
hello @crramirez quick question do you know how the /etc/boot.d work, I have enabled it using pengwin-setup. is it like init.d and rcS.d? right now I have the following in rcS.d even though S01screen-cleanup -> ../init.d/screen-cleanup is there and in init.d the screen-cleanup script is executable it does not execute at startup. Do I need to put something in /etc/boot.d ? dos /etc/boot.d wotk the same Sxx.... or Kxx..., I will play with it and see.. thank you FYI, I tried to add S01screen-cleanup -> /etc/init.d/screen-cleanup to the /etc/boot.d folder but it does not execute either. |
|
Hello @puskyer It is indeed a hack. What pengwin does is execute the scripts in boot.d You can put the scripts you want to be started in /etc/boot.d or enable SystemD Regards, |
|
Thank you will try that..
Cheers
Get BlueMail for Android
…On Feb. 16, 2023, 4:57 p.m., at 4:57 p.m., Carlos Rafael Ramirez ***@***.***> wrote:
Hello @puskyer
It is indeed a hack. What pengwin does is execute the scripts in boot.d
`run-parts /etc/boot.d` when the shell is started. It doesn't have
anything to do with /etc/init.d
You can put the scripts you want to be started in /etc/boot.d or enable
SystemD
Regards,
Carlos
--
Reply to this email directly or view it on GitHub:
#763 (comment)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Describe the bug
when I first install screen it works, after shutting down mu notebook and rebooting it, screen returns "Cannot make directory '/run/screen': Permission denied"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
screen command to work
Screenshots
after notebook reboot
#################
~$ screen
Cannot make directory '/run/screen': Permission denied
~$ /etc/init.d/screen-cleanup
~$ screen
Cannot make directory '/run/screen': Permission denied
~$ sudo /etc/init.d/screen-cleanup
[sudo] password for pusky:
~$ screen
Cannot make directory '/run/screen': Permission denied
$ sudo apt purge screenbpo11+1) ...[sudo] password for pusky:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
screen*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 1,038 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 65954 files and directories currently installed.)
Removing screen (4.8.0-6) ...
Processing triggers for man-db (2.10.1-1
(Reading database ... 65895 files and directories currently installed.)
Purging configuration files for screen (4.8.0-6) ...
removed '/etc/tmpfiles.d/screen-cleanup.conf'
$ sudo apt install screenbpo11+1) ...Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
byobu | screenie | iselect ncurses-term
The following NEW packages will be installed:
screen
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 609 kB of archives.
After this operation, 1,038 kB of additional disk space will be used.
Get:1 https://deb.debian.org/debian bullseye/main amd64 screen amd64 4.8.0-6 [609 kB]
Fetched 609 kB in 1s (749 kB/s)
Selecting previously unselected package screen.
(Reading database ... 65893 files and directories currently installed.)
Preparing to unpack .../screen_4.8.0-6_amd64.deb ...
Unpacking screen (4.8.0-6) ...
Setting up screen (4.8.0-6) ...
Processing triggers for man-db (2.10.1-1
~$ screen
[screen is terminating]
~$
################
Additional context
this happens everytime I reboot my notebook or terminate the wsl session.
Basic Troubleshooting Checklist
[ ] I have searched Google for the error message. (Yes)
[ ] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled.
[ ] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues. (yes) "FYI: Search filter was is:issue is:open,closed '/run/screen' in:title,body"
[ ] I have searched the Pengwin issues page: https://github.com/WhitewaterFoundry/Pengwin/issues. (yes)
[ ] I have run Windows 10 updates and restarted. (Yes)
[ ] I have restarted WSL service:
wsl.exe --terminate WLinuxwsl.exe --shutdown. (yes)What other troubleshooting have you attempted?
########
~$ /etc/init.d/screen-cleanup
~$ screen
Cannot make directory '/run/screen': Permission denied
~$ sudo /etc/init.d/screen-cleanup
[sudo] password for pusky:
~$ screen
Cannot make directory '/run/screen': Permission denied
#######
~$ mkdir ~/.screen && chmod 700 ~/.screen
~$ export SCREENDIR=$HOME/.screen
~$ screen
[screen is terminating]
~$
#########
Pengwin Version
PENGWIN_VERSION="22.11.4"
WSL general info
Release Install Date: Wed Dec 28 13:03:22 EST 2022
Branch: vb_release
Build: 19045
Full Build: 19041.1.amd64fre.vb_release.191206-1406
Display Scaling: 1
Locale (Windows): en_CA
Theme (Windows): dark
Uptime (Windows): 4d 20h 3m
Version (WSL): 2
Uptime (WSL): 0d 0h 29m
Release: Pengwin
Kernel: Linux 5.15.79.1-microsoft-standard-WSL2
Packages: 975
IPv4 Address: 172.21.184.154
System Type (Windows): Desktop
SystemD Status: disabled
The text was updated successfully, but these errors were encountered: