gui rpc?

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

wow MUCH better! thank you. i

Message 90409 in response to message 90408

wow MUCH better! thank you. i dont have a screen reader for windows sadly, so the big font is a real help, thanks.

o.k. i didnt think of the reboot, still get the error, as requested.

[pre]
paul@linux-laptop:~$ ls -l /home/paul/Desktop/remote_hosts.cfg
-rw-r--r-- 1 paul paul 43 2009-02-01 21:53 /home/paul/Desktop/remote_hosts.cfg
paul@linux-laptop:~$ ls -l /etc
total 1440
drwxr-xr-x 8 root root 4096 2009-01-16 12:16 acpi
-rw-r--r-- 1 root root 2986 2008-10-29 18:54 adduser.conf
-rw-r--r-- 1 root root 45 2009-02-10 07:46 adjtime
drwxr-xr-x 2 root root 4096 2009-02-08 21:46 alternatives
-rw-r--r-- 1 root root 395 2008-09-02 19:37 anacrontab
drwxr-xr-x 7 root root 4096 2008-10-29 19:06 apm
drwxr-xr-x 2 root root 4096 2009-01-16 12:26 apparmor
drwxr-xr-x 6 root root 4096 2009-01-16 12:25 apparmor.d
drwxr-xr-x 3 root root 4096 2008-10-29 19:06 apport
drwxr-xr-x 4 root root 4096 2009-01-19 09:56 apt
-rw-r----- 1 root daemon 144 2008-07-10 11:01 at.deny
drwxr-xr-x 3 root root 4096 2009-01-16 12:16 avahi
-rw-r--r-- 1 root root 1733 2008-05-12 14:48 bash.bashrc
-rw-r--r-- 1 root root 216757 2008-06-19 15:18 bash_completion
drwxr-xr-x 2 root root 4096 2009-02-08 23:35 bash_completion.d
drwxr-xr-x 2 root root 4096 2008-10-29 18:53 belocs
-rw-r--r-- 1 root root 332 2008-09-29 05:20 bindresvport.blacklist
-rw-r--r-- 1 root root 386 2009-02-08 21:41 blkid.tab
-rw-r--r-- 1 root root 386 2009-01-16 12:24 blkid.tab.old
drwxr-xr-x 2 root root 4096 2008-10-29 19:11 bluetooth
-rw-r--r-- 1 root root 6924 2008-06-18 23:52 bogofilter.cf
drwxrwxr-x 2 root root 4096 2009-02-08 23:35 boinc-client
drwxr-xr-x 2 root root 4096 2008-10-29 19:02 bonobo-activation
-rw-r--r-- 1 root root 33 2008-10-29 19:10 brlapi.key
drwxr-xr-x 2 root root 4096 2008-10-29 19:10 brltty
-rw-r--r-- 1 root root 15596 2008-08-06 05:09 brltty.conf
drwxr-xr-x 3 root root 4096 2008-10-29 18:54 ca-certificates
-rw-r--r-- 1 root root 6256 2009-01-16 12:16 ca-certificates.conf
-rw-r--r-- 1 root root 6204 2008-10-29 18:54 ca-certificates.conf.dpkg-old
drwxr-xr-x 2 root root 4096 2008-10-29 19:05 calendar
drwxr-s--- 2 root dip 4096 2009-01-16 12:16 chatscripts
drwxr-xr-x 2 root root 4096 2008-10-29 19:07 compizconfig
drwxr-xr-x 4 root root 4096 2008-10-29 18:58 ConsoleKit
drwxr-xr-x 2 root root 4096 2009-01-16 12:25 console-setup
drwxr-xr-x 3 root root 4096 2008-10-29 19:02 console-tools
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 cron.d
drwxr-xr-x 2 root root 4096 2009-02-08 22:13 cron.daily
drwxr-xr-x 2 root root 4096 2008-10-29 19:05 cron.hourly
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 cron.monthly
-rw-r--r-- 1 root root 724 2008-09-09 15:46 crontab
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 cron.weekly
drwxr-xr-x 4 root lp 4096 2009-01-16 12:25 cups
drwxr-xr-x 5 root root 4096 2008-10-29 19:10 dbus-1
-rw-r--r-- 1 root root 2969 2008-10-10 06:32 debconf.conf
-rw-r--r-- 1 root root 10 2007-04-01 07:47 debian_version
drwxr-xr-x 2 root root 4096 2009-02-08 23:35 default
drwxr-xr-x 4 root root 4096 2008-10-29 19:04 defoma
-rw-r--r-- 1 root root 600 2008-06-26 04:33 deluser.conf
drwxr-xr-x 2 root root 4096 2008-10-29 18:54 depmod.d
drwxr-xr-x 4 root root 4096 2008-10-29 18:54 dhcp3
drwxr-xr-x 2 root root 4096 2008-10-29 19:15 dictionaries-common
drwxr-xr-x 3 root root 4096 2009-01-16 12:53 dkms
drwxr-xr-x 2 root root 4096 2008-10-15 05:56 dm
drwxr-xr-x 3 root root 4096 2008-10-29 19:00 doc-base
drwxr-xr-x 3 root root 4096 2008-10-29 18:53 dpkg
-rw-r--r-- 1 root root 34 2008-02-18 23:33 e2fsck.conf
drwxr-xr-x 3 root root 4096 2008-10-29 18:59 emacs
-rw-r--r-- 1 root root 79 2008-10-29 18:53 environment
drwxr-xr-x 2 root root 4096 2008-10-29 19:02 esound
drwxr-xr-x 2 root root 4096 2008-10-29 19:15 event.d
drwxr-xr-x 4 root root 4096 2008-10-29 19:01 firefox-3.0
drwxr-xr-x 4 root root 4096 2008-10-29 19:02 fonts
drwxr-xr-x 3 root root 4096 2008-10-29 19:02 foomatic
-rw-r--r-- 1 root root 480 2009-01-14 15:30 fstab
-rw-r----- 1 root fuse 216 2008-09-25 12:06 fuse.conf
-rw-r--r-- 1 root root 2689 2008-03-26 13:44 gai.conf
drwxr-xr-x 2 root root 4096 2008-10-29 19:10 gamin
drwxr-xr-x 7 root root 4096 2008-10-29 18:58 gconf
drwxr-xr-x 7 root root 4096 2009-02-08 22:27 gdm
drwxr-xr-x 3 root root 4096 2008-10-29 19:01 gimp
drwxr-xr-x 3 root root 4096 2008-10-29 19:04 gnome
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 gnome-app-install
drwxr-xr-x 3 root root 4096 2008-10-29 19:01 gnome-system-tools
drwxr-xr-x 3 root root 4096 2008-10-29 18:58 gnome-vfs-2.0
-rw-r--r-- 1 root root 10852 2007-04-27 22:27 gnome-vfs-mime-magic
drwxr-xr-x 2 root root 4096 2009-01-16 12:18 gre.d
drwxr-xr-x 2 root root 4096 2008-10-29 19:05 groff
-rw-r--r-- 1 root root 875 2009-02-09 08:09 group
-rw------- 1 root root 871 2009-02-09 08:05 group-
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 grub.d
-rw-r----- 1 root shadow 724 2009-02-09 08:09 gshadow
-rw------- 1 root root 720 2009-02-09 08:05 gshadow-
drwxr-xr-x 2 root root 4096 2008-10-29 19:02 gtk-2.0
drwxr-xr-x 3 root root 4096 2008-10-29 19:01 hal
-rw-r--r-- 1 root root 4793 2008-06-19 04:46 hdparm.conf
-rw-r--r-- 1 root root 418 2008-10-29 19:08 hesiod.conf
-rw-r--r-- 1 root root 92 2008-08-08 13:53 host.conf
-rw-r--r-- 1 root root 13 2009-01-14 15:25 hostname
-rw-r--r-- 1 root root 248 2009-01-14 15:25 hosts
-rw-r--r-- 1 root root 579 2008-10-29 19:08 hosts.allow
-rw-r--r-- 1 root root 878 2008-10-29 19:08 hosts.deny
drwxr-xr-x 2 root root 4096 2008-10-29 19:04 hp
drwxr-xr-x 2 root root 4096 2008-10-29 19:08 hwtest.d
-rw-r--r-- 1 root root 73 2009-02-08 22:13 inetd.conf
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 init.d
drwxr-xr-x 5 root root 4096 2009-01-16 12:21 initramfs-tools
-rw-r--r-- 1 root root 1723 2007-10-02 10:35 inputrc
drwxr-xr-x 2 root root 4096 2008-10-29 18:54 iproute2
-rw-r--r-- 1 root root 19 2008-10-20 08:27 issue
-rw-r--r-- 1 root root 12 2008-10-20 08:27 issue.net
drwxr-xr-x 3 root root 4096 2008-10-29 19:02 kbd
drwxr-xr-x 5 root root 4096 2008-10-29 19:15 kernel
-rw-r--r-- 1 root root 167 2009-01-14 15:28 kernel-img.conf
drwxr-xr-x 10 root root 4096 2008-10-29 19:06 laptop-mode
drwxr-xr-x 2 root root 4096 2009-02-08 21:43 ldap
-rw-r--r-- 1 root root 58751 2009-02-09 03:08 ld.so.cache
-rw-r--r-- 1 root root 34 2008-10-29 18:53 ld.so.conf
drwxr-xr-x 2 root root 4096 2009-02-08 21:30 ld.so.conf.d
-rw-r--r-- 1 root root 3578 2008-10-10 10:47 lftp.conf
-rw-r--r-- 1 root root 20 2008-05-02 21:24 libao.conf
drwxr-xr-x 2 root root 4096 2008-06-19 08:59 libpaper.d
-rw-r--r-- 1 root root 2586 2008-03-11 07:02 locale.alias
-rw-r--r-- 1 root root 3519 2009-01-14 15:26 localtime
drwxr-xr-x 5 root root 4096 2008-10-29 19:00 logcheck
-rw-r--r-- 1 root root 9676 2009-02-09 08:05 login.defs
-rw-r--r-- 1 root root 599 2008-10-09 03:11 logrotate.conf
drwxr-xr-x 2 root root 4096 2009-02-08 22:13 logrotate.d
drwxr-xr-x 2 root root 4096 2008-09-16 08:53 lsb-base
-rw-r--r-- 1 root root 3820 2008-03-10 15:00 lsb-base-logging.sh
-rw-r--r-- 1 root root 99 2008-10-20 08:07 lsb-release
-rw-r--r-- 1 root root 13144 2008-07-02 12:00 ltrace.conf
-rw-r--r-- 1 root root 111 2008-07-11 06:22 magic
-rw-r--r-- 1 root root 111 2008-07-11 06:22 magic.mime
-rw-r--r-- 1 root root 20113 2009-02-08 21:43 mailcap
-rw-r--r-- 1 root root 449 2008-06-19 08:50 mailcap.order
-rw-r--r-- 1 root root 4630 2008-07-11 11:02 manpath.config
-rw-r--r-- 1 root root 21373 2008-06-19 08:50 mime.types
-rw-r--r-- 1 root root 803 2008-10-13 09:09 mke2fs.conf
drwxr-xr-x 3 root root 4096 2009-02-09 03:08 modprobe.d
-rw-r--r-- 1 root root 208 2009-01-14 15:27 modules
drwxr-xr-x 4 root root 4096 2008-10-29 19:07 mono
lrwxrwxrwx 1 root root 13 2009-01-14 15:07 motd -> /var/run/motd
-rw-r--r-- 1 root root 346 2008-10-29 18:54 motd.tail
-rw-r--r-- 1 root root 754 2009-02-10 07:49 mtab
-rw-r--r-- 1 root root 624 2008-05-29 16:55 mtools.conf
drwxr-xr-x 3 root root 4096 2009-01-16 14:02 mysql
-rw-r--r-- 1 root root 7672 2008-09-24 04:37 nanorc
-rw-r--r-- 1 root root 2064 2006-11-23 14:33 netscsid.conf
drwxr-xr-x 6 root root 4096 2008-10-29 18:54 network
drwxr-xr-x 4 root root 4096 2009-01-16 12:20 NetworkManager
-rw-r--r-- 1 root root 91 2008-08-08 13:53 networks
-rw-r--r-- 1 root root 513 2008-10-29 19:13 nsswitch.conf
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 obex-data-server
drwxr-xr-x 2 root root 4096 2009-01-16 12:25 openoffice
drwxr-xr-x 2 root root 4096 2008-10-29 18:53 opt
-rw-r--r-- 1 root root 552 2008-10-16 00:32 pam.conf
drwxr-xr-x 2 root root 4096 2009-02-08 22:13 pam.d
drwxr-xr-x 2 root root 4096 2008-10-29 19:02 pango
-rw-r--r-- 1 root root 7 2009-01-14 15:27 papersize
-rw-r--r-- 1 root root 1525 2009-02-08 23:36 passwd
-rw------- 1 root root 1505 2009-02-08 23:35 passwd-
drwxr-xr-x 2 root root 4096 2008-10-29 19:08 pcmcia
drwxr-xr-x 5 root root 4096 2008-10-29 19:06 perl
drwxr-xr-x 5 root root 4096 2008-10-29 19:01 pm
-rw-r--r-- 1 root root 7649 2008-10-29 19:08 pnm2ppa.conf
drwxr-xr-x 2 root root 4096 2008-10-29 19:10 PolicyKit
-rw-r--r-- 1 root root 343 2009-01-19 09:56 popularity-contest.conf
drwxr-xr-x 4 root root 4096 2008-10-29 19:00 power
drwxr-xr-x 8 root dip 4096 2009-01-16 12:16 ppp
-rw-r--r-- 1 root root 497 2009-01-16 11:57 profile
drwxr-xr-x 2 root root 4096 2008-10-29 19:07 profile.d
-rw-r--r-- 1 root root 2626 2008-06-23 11:12 protocols
drwxr-xr-x 2 root root 4096 2009-02-08 21:51 pulse
drwxr-xr-x 2 root root 4096 2008-10-29 19:08 purple
drwxr-xr-x 2 root root 4096 2008-10-29 18:54 python
drwxr-xr-x 2 root root 4096 2008-10-29 18:53 python2.5
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc0.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc1.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc2.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc3.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc4.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc5.d
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rc6.d
-rwxr-xr-x 1 root root 306 2008-10-29 18:54 rc.local
drwxr-xr-x 2 root root 4096 2009-02-09 03:08 rcS.d
drwxr-xr-x 2 root root 4096 2008-10-29 19:08 readahead
drwxr-xr-x 3 root root 4096 2008-10-29 19:00 resolvconf
-rw-r--r-- 1 root root 53 2009-02-10 07:49 resolv.conf
-rwxr-xr-x 1 root root 268 2008-05-03 03:40 rmt
-rw-r--r-- 1 root root 887 2008-06-23 11:12 rpc
drwxr-xr-x 2 root root 4096 2009-02-08 22:13 samba
drwxr-xr-x 3 root root 4096 2008-10-29 19:08 sane.d
drwxr-xr-x 2 root root 4096 2008-10-29 19:10 scim
-rw-r--r-- 1 root root 3663 2008-06-13 05:59 screenrc
-rw-r--r-- 1 root root 1254 2008-06-09 14:10 securetty
drwxr-xr-x 2 root root 4096 2009-01-16 11:57 security
-rw-r--r-- 1 root root 71449 2008-09-09 16:31 sensors3.conf
-rw-r--r-- 1 root root 85602 2008-07-04 04:09 sensors.conf
-rw-r--r-- 1 root root 18449 2008-06-23 11:12 services
drwxr-xr-x 3 root root 4096 2008-10-29 19:04 sgml
-rw-r----- 1 root shadow 907 2009-02-08 23:35 shadow
-rw------- 1 root root 907 2009-02-08 23:35 shadow-
-rw-r--r-- 1 root root 192 2009-02-09 08:05 shells
drwxr-xr-x 2 root root 4096 2008-10-29 19:00 skel
drwxr-xr-x 3 root root 4096 2008-10-29 18:58 sound
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 ssh
drwxr-xr-x 4 root root 4096 2009-01-16 12:15 ssl
-r--r----- 1 root root 557 2009-01-14 15:24 sudoers
-rw-r--r-- 1 root root 2281 2008-10-27 07:16 sysctl.conf
drwxr-xr-x 2 root root 4096 2009-01-16 12:19 sysctl.d
-rw-r--r-- 1 root root 1626 2008-08-29 20:40 syslog.conf
drwxr-xr-x 2 root root 4096 2008-10-29 18:53 terminfo
-rw-r--r-- 1 root root 17 2009-01-14 15:26 timezone
-rw-r--r-- 1 root root 645 2008-02-08 12:31 ts.conf
-rw-r--r-- 1 root root 1260 2008-05-30 02:22 ucf.conf
drwxr-xr-x 3 root root 4096 2009-01-16 12:21 udev
drwxr-xr-x 3 root root 4096 2009-02-08 21:43 ufw
-rw-r--r-- 1 root root 142 2008-07-18 09:09 uniconf.conf
-rw-r--r-- 1 root root 214 2008-06-26 10:17 updatedb.conf
drwxr-xr-x 2 root root 4096 2009-01-16 12:16 update-manager
drwxr-xr-x 2 root root 4096 2008-10-24 01:57 update-notifier
-rw-r--r-- 1 root root 117 2009-01-14 15:27 usplash.conf
drwxr-xr-x 2 root root 4096 2009-02-08 21:43 vim
drwxr-xr-x 2 root root 4096 2008-10-29 19:06 w3m
-rw-r--r-- 1 root root 4221 2008-07-25 03:27 wgetrc
-rw-r--r-- 1 root root 1343 2007-01-09 13:39 wodim.conf
drwxr-xr-x 2 root root 4096 2008-10-29 19:08 wpa_supplicant
-rw-r----- 1 root dialout 66 2008-10-29 19:10 wvdial.conf
drwxr-xr-x 9 root root 4096 2008-10-29 19:17 X11
drwxr-xr-x 5 root root 4096 2008-10-29 19:10 xdg
drwxr-xr-x 2 root root 4096 2008-10-29 19:03 xml
drwxr-xr-x 2 root root 4096 2009-01-16 12:18 xulrunner-1.9
-rw-r--r-- 1 root root 461 2008-04-03 15:33 zsh_command_not_found
[/pre]

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Gundolf Jahn
Gundolf Jahn
Joined: 1 Mar 05
Posts: 1,079
Credit: 341,280
RAC: 0

RE: wow MUCH better! thank

Message 90410 in response to message 90409

Quote:
wow MUCH better! thank you. i dont have a screen reader for windows sadly, so the big font is a real help, thanks.


If you are using MS Internet Explorer, then you can turn off the formatting of the websites, so that you can use the font size settings of the View menu. I have the German version, so I can only guess the correct menu names, but it should be under Tools (Extras) / Web options (Internetoptionen). There in the lower right-hand corner is a button for Input assistance (Eingabehilfen), where you can turn off the specifications of the website (Schriftgradangaben auf Webseiten ignorieren).

Then, as mentioned before, you can set the font size (Schriftgrad) to very big in the View (Ansicht) menu of the browser.

If you are using another browser, I'm sure that there are similar options.

Gruß,
Gundolf

Computer sind nicht alles im Leben. (Kleiner Scherz)

Dagorath
Dagorath
Joined: 22 Apr 06
Posts: 146
Credit: 226,423
RAC: 0

RE: drwxrwxr-x 2 root root

Message 90411 in response to message 90409

Quote:
drwxrwxr-x 2 root root 4096 2009-02-08 23:35 boinc-client

There ya go. Your paul account doesn't have permission to write files in the boinc-client directory because boinc-client is owned by root. Only root and members of the root group can do that. Your options are:

1) become root to cp remote_hosts.cfg to /etc/boinc-client - works but it doesn't give paul the option to write to /etc/boinc-client in the future.
2) give everybody permission to write to /etc/boinc-client - works but your system is less secure when everybody can write anywhere
3) put /etc/boinc-client in the boinc group - paul is already a member of boinc group so he will always be aable to write there, I like this solution best

You can implement 3) with sudo chown root:boinc /etc/boinc-client. Then you should be able to copy remote_hosts.cfg to /etc/boinc-client. However, boinc owns the boinc-client executable and boinc-client runs under boinc's account but etc/boinc-client/remote_hosts.cfg will be owned by paul since paul created it so you need to set its group or ownership or permissions to allow the boinc executable to read it. Your options there are:

1) give everybody read permission - everybody means hackers too, you don't want that
2) make boinc the owner and put it in boinc group - keeps everybody else out but you can still read/write to it since you are a member of boinc group and boinc can read/write it since boinc owns it

If you like 2) then after you do the copy do:
sudo chown boinc:boinc /etc/boinc-client/remote_hosts.cfg - changes owner and group to boinc
sudo chmod u+rw /etc/boinc-client/remote_hosts.cfg - allows the file's owner to read/write to it, owner probably already has this permissions but we'll just make sure, the u in "u+rw" specifies owner
sudo chmod g+rw /etc/boinc-client/remote_hosts.cfg - allows the file's group members to read/write to it, the g in "g+rw" specifies group
sudo chmod o-rw /etc/boinc-client/remote_hosts.cfg - removes permissions for others to read/write, the o in "o+rw" specifies others

You may run into other problems getting your plan to work. In so many cases it's just a simple file permissions problem. Always think about which user owns the file or directory in question, who needs read or write permission to the file/directory in question and, for sake of security, who does NOT need to access it. Then you need to understand how the various commands manipulate the ownership, group and read/write permissions. That's the part that's not so obvious, let me see if I can find a good online tutorial on permissions for you.

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

thank you, very

Message 90412 in response to message 90411

thank you, very informative!

[pre]
paul@linux-laptop:~$ sudo chown root:boinc /etc/boinc-client
[sudo] password for paul:
paul@linux-laptop:~$ cp /home/paul/Desktop/remote_hosts.cfg /etc/boinc-client
cp: cannot create regular file `/etc/boinc-client/remote_hosts.cfg': Permission denied
paul@linux-laptop:~$ ls -l /etc/boinc-client
total 16
-rw-r--r-- 1 root boinc 1225 2008-07-15 13:18 cc_config.xml
-rw-rw-r-- 1 root boinc 298 2008-07-15 13:18 global_prefs_override.xml
-rw-r----- 1 root boinc 1 2008-07-15 13:18 gui_rpc_auth.cfg
-rw-r--r-- 1 root boinc 296 2008-07-15 13:18 remote_hosts.cfg
paul@linux-laptop:~$ cp /home/paul/Desktop/gui_rpc_auth.cfg /etc/boinc-client
cp: cannot create regular file `/etc/boinc-client/gui_rpc_auth.cfg': Permission denied
[/pre]

hmm, maybe im missing a step.

well im not going to give up, and im still learning. took me a while to realize file/directory names in linux are CASE sensative, man that gave me a headache figuring out but now that i know i pay closer attention.

edit: just realized that only showd the files IN boinc-client not boinc-client itself. hey, see, im learning!

[pre]
drwxrwxr-x 2 root boinc 4096 2009-02-08 23:35 boinc-client
[/pre]

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Dagorath
Dagorath
Joined: 22 Apr 06
Posts: 146
Credit: 226,423
RAC: 0

yes, you did miss a step and

Message 90413 in response to message 90412

yes, you did miss a step and the following tells us which step you missed

Quote:
[pre]drwxrwxr-x 2 root boinc 4096 2009-02-08 23:35 boinc-client[/pre]

To understand, you need to know what the drwxrwxr-x string means. That string is called "the permission bits" though it gives a little more info than just the permissions.

The first position on the left is either:

  • *

d - it's a directory
* l - it's a link (like a Windows shortcut, not the actual file just a link to a file)
* - - a regular file (an executable, a text file, a graphic file, etc).
The remaining 9 bits are divided into triads (groups of 3). The left-most triad is for the file's owner (user), the middle triad is for the file's group, the right-most triad is for others where others means all those who are neither the file's owner nor in the file's group, in other words the rest of the world.

Because owner and others both start with letter o, we refer to the owner as user and deignate the 3 groups with 3 letters for brevity:

  • u = owner
    g = group
    o = others

Now we can show the relationship between the triads and the people this way:
[pre]
u g o
d|---|---|---
[/pre]

Each triad designates 3 permissions in the following order from left to right:

  • * r = read = can read the file or directory
    * w = write = can write to the file or directory, if the file is a directory then can create and delete files in that directory
    * x = executable = can cd to the file if the file is a directory or can execute it if it's an executable

The bits in the triads are either "on" (an r, w or x) or "off" (a -).

Some examples:

  • *

-rw-rw-rw- means everybody can read and write to the file, not very secure but you might fins a use for it
* -rw-r-r- means everybody can read the file but only the owner can write to it, more secure but not what you would want for a file containing a password
* -r-------- means only the owner can read and NOBODY can write, very secure, so secure even the owner must jump through some hoops just to write to it (you have become root and give yourself write permission first) but if you need to hide something important this helps
* -rw-rw---- means the owner and members of the group can read and write, good for files that a team collaborates on, the administrator simply gives membership in the group to trusted users, the rest of the world is blocked

Changing permissions is easy with the chmod command. Only the file's owner and root can change permissions, group members cannot. Some examples:

chmod g-rw foo - removes read and write permissions for groups for the file named foo
chmod g+r foo - adds read permissions for groups for the file named foo
chmod o-rw foo - removes read and write permissions for others for the file named foo

It is not an error to turn on a permission that is already turned on or turn one off that is already off. The best way to learn chmod is to create a test file and play with the permissions. Do not play with the d bit (the directory bit) with chmod, it's not that simple. But do experiment with giving yourself read and write permission to directories as well as regular files.
Now back to the permissions for your /etc/boinc-client directory, I'll split it up into the triads:

Quote:
[pre]d | rwx | rwx | r-x 2 root boinc 4096 2009-02-08 23:35 boinc-client[/pre]

From the underlined info we see that root is the owner and boinc is the group. From the 3rd and 6th bits, I've bolded them, we see that the owner and group can write to the directory. The - in the 9th bit tells us others cannot write to that directory. Since it's only the others who cannot write to the directory then it appears that you are just one of the others and not a member of boinc group. If you were a member of boinc group or root then you could write, we know that from the 6th bit. In order to create a file in a directory or even copy a file to a directory the w bit must be turned on for you or a group in which you have membership.

So if you prefix the cp command with sudo then the file will copy because root is the owner and even if root is not the owner he can do anything. But think about the future... do you really want to have to become root each and every time you want to modify one of boinc's files? Isn't it easier just to give yourself membership in the boinc group? If your username is paul then the following command will make you a member of boinc group. If your username is not paul then put your actual username where you see paul:

[pre]sudo usermod -G boinc -a paul[/pre]

If you get a "file not found" error from the above command, that tells you usermod is not on root's path. The path might be /usr/sbin/usermod on Ubuntu but I'm not sure, you'll have to search your disk for it.

There, now you have everything you need to solve the problem, including a fairly thorough (but by no means complete) explanation of how to read the permissions, some security considerations and how to change the permissions. You can figure it out from the info I've given you.

I strongly suggest NOT runing with the --allow_remote_hosts option as suggested by one of the other posters because there is very little security in BOINC on Ubuntu to start with and using --allow_remote_hosts defeats that. That's why I recommend Fedora over Ubuntu.

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

amazingly enough, i

Message 90414 in response to message 90413

amazingly enough, i understood that :| lol thanks.
[pre]
paul@linux-laptop:~$ sudo usermod -G boinc -a paul
[sudo] password for paul:
paul@linux-laptop:~$
[/pre]

im guessing by the fact there is no error shown, it was ran properly, but it still will not let me write the file. ah well. i have learnd quight a bit from this thread.

ive tryd fedora once on that system but was unable to get the wireless to work, infact to get it to work in ubuntu i had to tell ubuntu it was a hidden network (which its not) and then have it "force" the connection. under fedora it couldnt see the wireless card, or, i didnt/dont have the knowledge to properly troubleshoot hardware issues.

otherwise id probably try fedora again and simply set up SSH and use putty on windows to connect. assuming i could change font attributes in putty (havent tryd that)

again, thank you for your time and help. i really apreciate it. and i finally know what all the "rwx" is about.

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Dagorath
Dagorath
Joined: 22 Apr 06
Posts: 146
Credit: 226,423
RAC: 0

You should be able to copy

Message 90415 in response to message 90414


You should be able to copy the file as root by putting sudo in front of the cpy command. But remember you'll also have to check the permissions on the file after you copy it because root will own it (since root created it). The client run on the boinc user account, not root. If you don't set (turn on) the read permission on the remote_hosts.cfg file, the client won't be able to read it. If the client can't read it then it won't allow a remote manager to connect.

If you get the remote_hosts.cfg copied and get permissions set right you need to reboot to force the client to read remote_hosts.cfg. Then if the remote manager still cannot connect, you need to look at your hosts file and hostname to address translation.

The other alternative is the --allow_remote_gui_rpc option which is not secure but if you're the only one using your system or you trust all the other users then it's good enough. If you block port 31416 in the firewall then nobody from outside can connect to the client. On Ubuntu, I think you need to edit /etc/init.d/boinc and uncomment the line that says #BOINCOPTS="--allow_remote_gui_rpc". Just remove the # sign at the start of the line. Be VERY careful what you do in that file. If you introduce even 1 extra space in the wrong place the daemon might not run.


paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

welp, ive progressed, i got

Message 90416 in response to message 90415

welp, ive progressed, i got SSH to work after figuring out i couldnt use the aptitude gui to do it. and ive been working all night in shell. so far i think ive progressed.

[pre]
-rw-rw---- 1 root boinc 9 2009-02-12 05:40 gui_rpc_auth.cfg
-rw-rw---- 1 root boinc 43 2009-02-12 05:41 remote_hosts.cfg
[/pre]

but when i issued /etc/init.d/boinc-client restart i got..

[pre]
paul@linux-laptop:/etc/boinc-client$ /etc/init.d/boinc-client restart
* Stopping BOINC core client: boinc
rm: cannot remove `/var/lib/boinc-client/lockfile': Permission denied

[/pre]

sorry if this looks weird, cant figure out how to copy specific lines in putty..

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35,825,044
RAC: 0

well i feel like an idiot,

Message 90417 in response to message 90416

well i feel like an idiot, but i got it to work! forgot to use sudo! i realized this after i stopped the client using the manager, then trying to start the client in the shell, still no go, then it hit me "duh" sudo /etc/init.d/boinc-client start. and there ya go, shes runnin. AND the remote host connected fine.

thank you, thank you, THANK YOU!

youve peakd my interest and now that i have putty working im going to be reading as much as i can. i doubt ill ever get in to the nuts and bolts, ive all ways wanted to learn to program and such, but dont have the memory retention for it. but ya never know :)

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Dagorath
Dagorath
Joined: 22 Apr 06
Posts: 146
Credit: 226,423
RAC: 0

Glad to hear you have the

Message 90418 in response to message 90417

Glad to hear you have the remote host connecting and all that.

I installed Ubuntu today just so I could have a better understanding of how the Ubuntu BOINC package works, what the problems are, etc. It's now obvious that the reason you were unable to copy ~/Desktop/remote_hosts.cfg to /etc/boinc-client/remote_hosts.cfg is that the installer creates a /etc/boinc-client/remote_hosts.cfg and gives the boinc group read permission on it but not write permission. If boinc group doesn't have write permission on /etc/boinc-client/remote_hosts.cfg then boinc group cannot copy over it. boinc group also needs write permission on /etc/boinc-client/ in order to copy files into it. So you need to do:

1) sudo usermod -G boinc -a paul
2) sudo chmod g+w /etc/boinc-client/remote_hosts.cfg
3) sudo chmod g+w /etc/boinc-client
3) sudo cp /home/paul/Desktop/remote_hosts.cfg /etc/boinc-client/remote_hosts.cfg

I think you already tried making paul a member of boinc group but perhaps did not run it with the sudo command in front so I'm suggesting to try it again.

If you can get your remote_hosts.cfg copied over then you should not need the --allow_remote_gui_rpc option but it's up to you whether you use it or not.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.