Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
All this is useless reading - jump straight to post #16
Hello, I've put together my home file server running debian wheezy and I have problems with transmission daemon rpc, the deamon itself is running but the server is not listening on the rpc port set in settings.json. Then I found out that settings.json is:
That looks fine to me now, as the daemon is ran by debian-transmission, but after i do reboot, permissions on setting.json are set back to 600. I do this via SSH and either as root or root group user.
Can anyone please help me? Why do those permissions reset after i reboot?
Also, to avoid creating another thread, different sort of question though, in windows, there is Device Manager which shows me all the devices and whether the drivers are installed/mising or there is a conflict on device. Is there any way how can I check this in linux cli? or at least xfce as I don't need gnome/kde/whatever on my server. Thank you for suggestions
everything works, but not right after the system boots. Well, I'll probably --purge remove a nd install the package again and will see, I'll report how it goes. To the second question, I don't have time now, have to go to work, but will tell you later whether that is what I thought because I never saw that command before
OK ... nothing worked so I reinstalled the system and it doesn't work on clean install either ...
I noticed that /etc/transmission-daemon's rights are drwxrws--- (what does the 's' stand for?)
tried chmod 770 but there is still the 's' right instead of 'x' for the owner which is debian-transmission
stat %a transmission-daemon says - Access: (2770/drwxrws---)
how do I change it to "real" 770? It looks like the user which runs the daemon can't access the file, because can't go into the directory where settings are located
That's called a sticky bit, setting g+s (group sticky) on a directory means that no matter which user creates a file in the directory it's group will be the same as the directory. This is a way of ensuring that the group who owns the directory will always have access to every file in it.
Ok .. reinstalled for 7th (yes, seventh!!!) time, and went step by step
1. clean install of debian
2. after reboot, apt-get update
3. then apt-get install transmission transmission-common transmission-daemon transmission-cli
4. after reboot, netstat shows connection on port 9091 (which is default), but as I have another daemon on NAS running on port 9091, I want to change the port to 9092
5. /etc/init.d/transmission-daemon stop (because I want to change the rpc port in settings.json)
6. now the test, right after "stop" I tried to start the daemon again and restart the computer without making any changes to settings.json, just stop and start the daemon, to see whether it still works
7. after reboot netstat shows no listening on 9091 or 9092
what the hell???????? I did all this via SSH as root
where do I make mistake? People, gurus, please help, I start to have grey hair from this
sorry for late reply, baby was crying all the time lol
nope, did netstat -el but tried -a now as well and can't see the port there
OK, no more reinstalls, tried to log daemon's activity, at least as much as is offered, here is the log:
[22:34:45.175] Transmission 2.52 (13304) started (session.c:718)
[22:34:45.175] RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:803)
[22:34:45.175] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:997)
[22:34:45.175] RPC Server Whitelist enabled (rpc-server.c:1001)
[22:34:45.175] UDP Failed to set receive buffer: requested 4194304, got 262142 (tr-udp.c:75)
[22:34:45.175] UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:80)
[22:34:45.175] UDP Failed to set send buffer: requested 1048576, got 262142 (tr-udp.c:86)
[22:34:45.175] UDP Please add the line "net.core.wmem_max = 1048576" to /etc/sysctl.conf (tr-udp.c:91)
[22:34:45.175] DHT Generating new id (tr-dht.c:309)
[22:34:45.175] Using settings from "/root/.config/transmission-daemon" (daemon.c:488)
[22:34:45.175] Saved "/root/.config/transmission-daemon/settings.json" (bencode.c:1731)
[22:34:45.175] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72)
[22:34:45.175] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:72)
[22:34:54.176] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.0.1:37215/ctrlu/WANIPConnection_3" (upnp.c:202)
[22:34:54.176] Port Forwarding (UPnP) Local Address is "192.168.0.13" (upnp.c:204)
[22:34:54.176] Port Forwarding (UPnP) Port forwarding through "http://192.168.0.1:37215/ctrlu/WANIPConnection_3", service "urn:schemas-upnp-org:service:WANIPConnection:1". (local address: 192.168.0.13:51413) (upnp.c:279)
[22:34:54.176] Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:93)
[22:34:54.176] Port Forwarding State changed from "Starting" to "???" (port-forwarding.c:93)
[22:35:17.177] DHT Attempting bootstrap from dht.transmissionbt.com (tr-dht.c:247)
yes, I got exactly what you wrote down, chuid is debian-transmission + all those paths are the same
but I can see where you point, but I was blind or it is way too late here and I'm waaay to tired lol
log says something about /root/.config/...... right, it should say /etc/tranmsission.....
but I don't know how the hell do I explain to that boody daemon to read from there lol
# defaults for transmission-daemon
# sourced by /etc/init.d/transmission-daemon
# Change to 0 to disable daemon
# This directory stores some runtime information, like torrent files
# and links to the config file, which itself can be found in
# Default options for daemon, see transmission-daemon(1) for more options
OPTIONS="--config-dir $CONFIG_DIR --logfile /var/log/transmission-daemon.log"
# (optional) extra options to start-stop-daemon
#START_STOP_OPTIONS="--iosched idle --nicelevel 10"