2014-03-02



I use mmh as mail client on the server. Mmh's tools aren't locat-
ed  in /usr/bin, but in /usr/local/mmh/bin (in my case). I have a
lot of scripts in ~/bin, too. This means, I need an adjusted PATH
environment variable. Everything fine so far.

Now, ssh(1) has this wonderful ability to run  a  single  command
from  remote,  like `ssh marmaro.de uptime'. I wanted to use this
approach to print a mail message, like this:

     ssh marmaro.de show l +in | lp

But the result was: ``mksh: show: not found''.

To solve this problem, you need to tell ssh, that it  should  not
set  up  a  clean  environment,  but take the user's environment.
Therefore     set      ``PermitUserEnvironment      yes''      in
/etc/ssh/sshd_config.

Then  you  need  to  define  the  path.  You   can   do   it   in
/etc/environment  for  the whole system, or in ~/.ssh/environment
for just this user's ssh sessions. I set PATH in both  locations,
with different values.

For debugging, use `ssh marmaro.de echo \$PATH'.


Today, I also put a new installation of Cubian on Klette.

It's always the same question:  How  do  I  change  the  timezone
correctly, on Debian system. This is how you should do it:

     dpkg-reconfigure tzdata


For some reason, I have problems unmounting NFS shares on  Klette
(the  Cubian machine). `umount /mm' results in the error message:
``umount.nfs4: /mm: not found''.  With the `-i' flag, umount does
no longer complain.


Also, I tried to access the scanner of the multi-function  device
Samsung SCX 4100. Of course, I tried Sane. And I used these pack-
ages: libsane-extras, pct-scanner-scripts, simple-scan.   But  it
didn't work. I had no prior experience with scanners and I didn't
read much about it before. I just thought, I could give it a try.
I  failed because the device wasn't recognized. As I don't really
need the scanner, I just stopped the try.


Unfortunately, I don't have a wired  internet  connection  in  my
computing  room.  This was okay to this day, because the Notebook
and the Cubietruck, both, have wifi modules. But Edoras, the  new
home  server, has not. I thought, that it should be no problem to
connect it directly to Klette, in an own  subset.  Then  I  could
route  the  packages as appropriate. Okay: fixed IP addresses for
Edoras and the wired socket of Klette. Then I needed to  activate
packet forwarding in Klette, because it acts as a gateway:

     echo 1 >/proc/sys/net/ipv4/conf/all/forwarding

And I needed to set the routes. (Correct /etc/hosts  entries  as-
sumed.) On Edoras:

     route add default gw klette
And on all the other machines in the normal network:

     route add edoras gw klette

Well, it works now, but it is terribly slow. I don't know why?



http://marmaro.de/lue/        markus schnalke <meillo@marmaro.de>