You are not logged in.
Pages: 1
hi,
i need to use the serial as user, so i've run "chmod o+rwx /run/lock ".
But after every reboot, the permission turn to change back to default.
It is normal? and why it is happening?
Offline
I don't understand the purpose of this, and I don't know if it would be a good idea ... but isn't /run recreated at boot in memory only?
If so you'd have to change the permissions after boot, perhaps in rc.local (again, I have no idea if this is a safe or good idea).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
the purpose of this is to use the serial as user.
with old /var/lock the permission was keep.. i wan't to understand why now they change
Offline
Isn't it enough to create a subdirectory with the correct access rights? Then create it in /etc/rc.local (sysvinit) or use /etc/tmpfiles.d/ (AFAIK systemd only)
The /run directory exists only in your main memory, so it has to be created at boottime.
Last edited by progandy (2012-06-15 19:35:30)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
ah ok, i don't thinks it is enougt to create the folder, i'm using an externelò lib, and i don't lnow if it support something similar.
Also this serial is over USB, so it's a little bit hard to know what USB nuber it will use
Offline
Sysvinit users get tmpfiles too. The only difference is the lack of a --clean action that systems users get periodically via a timer unit. /run/lock is going to be created via this mechanic. Not happy with the perms? Override the file from /usr/lib/tmpfiles.d in /etc/tmpfiles.d
Offline
/run/lock is created on boot by /usr/lib/tmpfiles.d/legacy.conf (both on systemd and initscripts). To overwrite it, simply copy the file to /etc/tmpfiles.d/ and edit it there. There should be a manpage to explain how it works, but in your case I guess you simply want to change the perms "0755" into whatever you need.
Offline
Pages: 1