Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I built a simple home server/WAP/ADSL gateway on a FreeBSD box and I've been running the transmission daemon to handle Bittorrent downloads. I access the downloaded files from a couple of desktop machines via NFS shares.
I took me awhile to figure out why the downloaded files were read-only on these NFS disks -- they are owned by UID 921, transmission-daemon. This makes managing downloaded files via Nautilus on the desktop boxes a bit cumbersome.
I'm wondering how others arrange this. Manually chown stuff? Or this there a smarter approach? I could run transmission-daemon with my own UID, but there are probably very good reasons why this is not a good idea
You're standard user account is a passwordless member of sudoers?
That's a bad idea.
Putting that information in a script?
Worse idea..."fire you on the spot" kind of bad idea, actually.
If you're just messing around, it's fine. If you're trying to learn a skill... read up on setfacl.
Your standard user account is a passwordless member of sudoers?
Nope. As mentioned above the /etc/rc.local runs sudo, and because it's root no passwords are asked for. No other user can sudo on this system (even though there's just the one).
Quote:
That's a bad idea.
Yep.
Quote:
Putting that information in a script?
Worse idea..."fire you on the spot" kind of bad idea, actually.
If you're just messing around, it's fine. If you're trying to learn a skill... read up on setfacl.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.