[BlueOnyx:10930] Re: Why refresh proftpd.conf when reboot ?

Eiji Hamano bluequartz at hypersys.ne.jp
Wed Jul 4 19:06:48 -05 2012


Hi  Greg.

>   If I were to guess, this would be related to the chrooting of end users 
> into a vsite environment.
>  The timezone file is in /etc/ ...
>
>  When a non-admin user logs in, it does a chroot. That chroot will not 
> have access to /etc ....

Wao!.  Good, You find out the root of the problem.

So,  the time-stamp difference between admin and non-admin happens in the 
world ?
It does't happens not only Japan ?   I  heard it the first time.
I  have not heard it in [BlueOnyx:03007]  Proftp timestamps.

Anyway,  it is my one step forward if you recognized the time-stamp 
difference..



>  Sorry to again say this, but please in future provide clear information 
> in reporting a bug.
>  We've wasted a lot of time talking about this in the list

Oh--.
Please try to insert  them in below.
You might placed them in place which does not function effectively.

# Normally, we want users to do a few things.
<Global>
AllowOverwrite          yes
TimesGMT           off                               <====  Add
SetEnv                TZ :/etc/localtime        <====  Add
ListOptions          "-a"                            <====  Add
  <Limit ALL SITE_CHMOD>
    AllowAll
  </Limit>


>  In my opinion, this symptom is NOT related to rebooting, nor is it 
> related to any blueonyx code changes.

Why?  Don't  you recognize the time-stamp difference,  do you?


Eiji Hamano




  ----- Original Message ----- 
  From: Greg Kuhnert
  To: blueonyx at mail.blueonyx.it
  Sent: Wednesday, July 04, 2012 8:04 PM
  Subject: [bluequartz] [BlueOnyx:10929] Re: Why refresh proftpd.conf when 
reboot ?


  Hi Eiji

  On 7/4/2012 3:17 PM, Eiji Hamano wrote:

    Hi  Chuck and Greg

    > That is your problem - right?

    It is great news.
    I  will be able to adapt it permanently to a specific server 
"ListOptions",
    until changing Proftp via YUM.

    However the time_stamp problem of Proftp is different from ListOptions.
    The problem might came from file /usr/share/zoneinfo,  I think.

    Greg

    I  created the clean test server that apply all yum updates.
    I will send the IP and psw to you personally.
    I pray that you are able to find out the root of the problem.

    The reproduce documenting are only 2 steps.

       1,  Access the server with ftp via  siteadmin,  not via admin.
           Only the problem happen on user and siteadmin,  Not on admin.

       2,  Please upload any file to any place on the server.
           Then look the time_stamp.

  On your server...

  1. I logged in. Edited /etc/proftpd.conf - and added a SetEnv TZ line
  2. Rebooted
  3. Config file was unchanged.

  The symptoms you reported initially "Why refresh proftpd.conf when reboot 
?" are untrue. BlueOnyx does NOT change or rebuild that file on reboot. 
Sorry to again say this, but please in future provide clear information in 
reporting a bug. We've wasted a lot of time talking about this in the list - 
where the problem you have reported does not exist.

  In your current email, you have now advised  that the timezone in log 
files is wrong when a non-admin user logs in. If I were to guess, this would 
be related to the chrooting of end users into a vsite environment.  The 
timezone file is in /etc/ ... When a non-admin user logs in, it does a 
chroot. That chroot will not have access to /etc .... If anyone knows how to 
configure a proftpd.conf file to overcome this problem, we can investigate 
new code for blueonyx to make this happen by default.

  In my opinion, this symptom is NOT related to rebooting, nor is it related 
to any blueonyx code changes. It would be a change in behavior for proftpd. 
It might be a good idea Eiji to go to the http://www.proftpd.org/ website 
and ask them for some help...

  Regards,
  Greg.



    Eiji Hamano




      No one will be able to make any FTP related changes - since that will 
lock the ProFTP configuration file.

      But if I remember that file correctly - it isn't updated each time a 
site is added/deleted.  Only when changes are made to the FTP configuration. 
So locking it won't hurt additions/deletions.  But if you want to modify the 
FTP server settings - you'd have to unlock the file first.

      The benefit - you won't have to worry about the proftpd.conf file 
updating each time the machine is rebooted.  That is your problem - right?



      Chuck



      ---------- Original Message ----------- 
      From: "Eiji Hamano" <bluequartz at hypersys.ne.jp>
      To: "BlueOnyx General Mailing List" <blueonyx at mail.blueonyx.it>
      Sent: Tue, 3 Jul 2012 16:22:14 +0900
      Subject: [BlueOnyx:10925]   Re: Why refresh proftpd.conf when reboot ?

      > Hi  Chuck
      >
      > While  "chattr +i /etc/proftpd.conf",
      > noone can create/delete/modify any site on  ADMIN page?
      >
      > Eiji Hamano
      >
      >

        > ----- Original Message ----- 
        > From: Chuck Tetlow
        > To: BlueOnyx General Mailing List
        > Sent: Tuesday, July 03, 2012 2:52 PM
        > Subject: [bluequartz] [BlueOnyx:10923] Re: Why refresh 
proftpd.conf when reboot ?
        >
        > This problem really seems to have dragged on for a long time, for 
such a small issue.
        >
        > Take the simple route Eiji while waiting on a fix.  If you can 
change the proftpd.conf file so it works the way you want it, and you don't 
want it changed from that configuration - set the file so it can't be 
changed.  Set the immutable bit on the file with "chattr +i 
/etc/proftpd.conf".  That will make the file completely unchangable - even 
by root.  You can see what files have what special permissions like 
immutable set with "lsattr /etc".  And if you ever want to change that file 
again, use "chattr -i /etc/proftpd.conf".
        >
        > This way, you don't have to worry about a reboot changing your 
ProFTP configuration file.  Its not the best solution - but will solve your 
immediate problem.
        >
        > Chuck
        >
        > ---------- Original Message ----------- 
        > From: "Eiji Hamano" <bluequartz at hypersys.ne.jp>
        > To: <blueonyx at mail.blueonyx.it>
        > Sent: Tue, 3 Jul 2012 14:20:53 +0900
        > Subject: [BlueOnyx:10922]   Re: Why refresh proftpd.conf when 
reboot ?
        >
        > > Hi  Greg
        > >
        > > I am glad to answer a clear reply.
        > > However,  you could not  imagine why I have to do it.
        > >
        > > See  [BlueOnyx:03007]  Proftp timestamps.
        > >
        > > And the link :
        > >  http://bluequartz.org/ml/archive/coba-e/15300/15357.html
        > > was gone.
        > > So See following "Original Message".
        > >
        > > > -----------Original Message----------------- 
        > > > Date: Wed, 18 Mar 2009 16:58:50 -0700
        > > > From: "Michael Aronoff" <ma at ciic.com>
        > > > Subject: [coba-e:15357] Proftp timestamps
        > > > To: <coba-e at bluequartz.org>
        > > >
        > > >
        > > > I have been having an issue with Proftp showing wrong 
timestamps for files
        > > > uploaded for a while.
        > > > It makes a mess of using Dream weavers sync functions.
        > > > I finally found a fix.  In case anyone else is interested.
        > > >
        > > > In /etc/proftpd.conf
        > > > In the <global> section
        > > > right below TimesGMT off
        > > > add the following line.
        > > > SetEnv TZ :/etc/localtime
        > > >
        > > > That will force proftp to get your timezone from the OS 
properly
        > > > and all timestamps shown in any FTP programs will be correct.
        > > > I hope someone finds it useful.  Perhaps it should be in BQ as 
a default?
        > > >
        > > > ___________________________
        > > > M Aronoff - West Hills, CA
        > >
        > > Eiji Hamano
        > >
        > > > Hi Eiji
        > > >
        > > > On 7/2/2012 1:10 PM, Eiji Hamano wrote:
        > > >> Hi  Chris
        > > >>
        > > >> Would you advice me how setting following  with GUI  ?
        > > >>
        > > >>     TimesGMT   off
        > > >>     SetEnv TZ :/etc/localtime
        > > >>     ListOptions   "-a"
        > > >
        > > > I just had a look at a stock Blueonyx box;
        > > >
        > > > 1. This is standard - no mods needed
        > > > TimesGMT                        off
        > > >
        > > > 2. This is also standard - no mods needed
        > > > ListOptions                     "-a"
        > > >
        > > > 3. The last one is an environment variable. If it is 
specifically
        > > > causing you grief, you can set it somewhere else - perhaps in 
an init or
        > > > rc script?
        > > >
        > > > As a more general answer to your question - Why refresh 
proftpd.conf?
        > > > Because it is designed that way. Way back in the bowels of 
time, the
        > > > Cobalt developers created constructors and handlers that build 
config
        > > > files based on data in the cobalt database. From my own 
experience, my
        > > > timestamps in my ftp log file work fine...
        > > >
        > > > Regards,
        > > > Greg
        > > >
        > > >> Eiji Hamano
        > > >>
        > > >>
        > > >>
        > > >>> Eiji Hamano wrote:
        > > >>>> Hi  Chris
        > > >>>>
        > > >>>>> Did you set the Time Zone in the BlueOnyx GUI?
        > > >>>> No,  I set them in "proftpd.conf ".
        > > >>> I would recommend setting in the BlueOnyx GUI.  That should 
help you.
        > > >>>
        > > >>>
        > > >>> -- 
        > > >>> Chris Gebhardt
        > > >>> VIRTBIZ Internet Services
        > > >>> Access, Web Hosting, Colocation, Dedicated
        > > >>> www.virtbiz.com | toll-free (866) 4 VIRTBIZ
        > >
        > > _______________________________________________
        > > Blueonyx mailing list
        > > Blueonyx at mail.blueonyx.it
        > > http://mail.blueonyx.it/mailman/listinfo/blueonyx
        > ------- End of Original Message ------- 
        >
        >
------------------------------------------------------------------------

        > _______________________________________________
        > Blueonyx mailing list
        > Blueonyx at mail.blueonyx.it
        > http://mail.blueonyx.it/mailman/listinfo/blueonyx
        >

      ------- End of Original Message ------- 



--------------------------------------------------------------------------
      _______________________________________________
      Blueonyx mailing list
      Blueonyx at mail.blueonyx.it
      http://mail.blueonyx.it/mailman/listinfo/blueonyx




_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx





------------------------------------------------------------------------------


  _______________________________________________
  Blueonyx mailing list
  Blueonyx at mail.blueonyx.it
  http://mail.blueonyx.it/mailman/listinfo/blueonyx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20120705/643237f2/attachment.html>


More information about the Blueonyx mailing list