[K12OSN] Re: rdesktop and windows terminal services & misc

[Matt Oquist]

--> rdesktop and windows terminal services
> >Has anyone one the list used rdesktop, and can it be used effectively as 
> >a client to terminal services.  I don't want to test it and recommend it 
> >if it does not work as advertised.

I used rdesktop regularly at my previous job.  I had M$ Office
& Project documents to edit, as well as the occasionaly IE-only
Intranet site to use.  rdesktop, in my experience, is far preferable
to the Citrix client I used previously.

rdesktop is very fast, highly scriptable and flexible.


--> samba-ldap script question (Tom Astle)
> I am using a FC3 installation and am trying to get roaming profiles
> to work for individual users. I have gotten to the point where the
> profile is being created upon login, but instead of being saved in
> /opt/samba/profiles/$username the profile is being stored in
> /opt/samba/profiles itself.
> 
> I looked at the LDAP record for the same user and this is the 
> setting:
> 
> sambaProfilePath: \\BOLTON-PDC\profiles
> 
> I thought the scripts were supposed to make directories per user by
> default?

None of the scripts make individual directories for roaming profiles,
but if this would be helpful it can certainly be added.

The scripts (by way of smbldap-useradd) make a home directory for each
user.

I just checked Dave's How-To (which ships inside the smbldap-installer
tarball) and his roaming profile are all stored in
/opt/samba/profiles, so that should work for other folks...

The danger with storing profiles inside the users' home directories is
that the users then have the power to delete or otherwise mangle them.
(And they're just sitting there like a big red button with a big
blinking sign - "Push Me!".)

If the smbldap-installer scripts should be enhanced to make this
easier for folks, just let me know what needs to be done, and while
I can't make any promises I can do my best to make this work better
for you all.

--> 6. Two related problems (Lee Harr)
> I looked at the dhcp lease, and the correct gateway is in the lease
> file, but the gateway is not being set.
> 
> I thought maybe the problem was with the firewall, but I reinstalled
> without the firewall and I have the same problem.
> 
> So, my question is ... to which file can I add a line like
> route add default gw 10.0.0.1
> which will be run at startup?

The real solution is to do what you've already tried - fix the problem
with DHCP not setting the gateway.

But you can do the following to hard-code the gateway on system
startup:
$ echo route add default gw 10.0.0.1 > /etc/init.d/gw-hack
$ chmod 755 /etc/init.d/gw-hack
$ cd /etc/rc5.d/
$ ln -s ../init.d/gw-hack S11gw-hack

The above is how you can create your own startup-script to do anything
you want.  I picked S11 because network startup is S10, and you want
to set the gateway after the network is started.

Also note that if you have any machines that don't boot into graphical
mode, the "runlevel" you want is 3, so you should put startup scripts
in the rc3.d directory instead.  (See /etc/inittab for your default
runlevel, and further documentation of all this.)

> 2nd question, which is related because the system is fine as long as
> no one reboots it is ... How do I keep regular users from rebooting
> the system?
> My solution was to chmod 0 /sbin/halt but that seems a bit drastic.

Yeah - I'd chmod 700 instead - /sbin/halt, /sbin/shutdown, and
/usr/bin/consolehelper (which is symlinked from /usr/bin/reboot).

Ah - and see /etc/inittab (again) to change what happens when a user
gives the three-finger salute: "CTRL-ALT-DEL".  Just find the
ctrlaltdel line and change the command it runs.  (For example: rm -rf
$HOME... ;)

--matt