On Mon, Jan 26, 2015 at 07:44:33PM +0100, Bert Freudenberg wrote:

I think I did set up a cronjob to generate the daily commit log. The script probably was in my user dir. Did that survive?

• Bert -

Yes your script and the cron job have survived.

According to the cron entry at /srv/box2/var/spool/cron/crontabs/squeaksource, cron entry was this:

55 23 * * * /home/squeaksource/dailycommits/dailycommits.sh

Your dailycommits.sh script and everything that goes with it is safely restored in /srv/box2/home/squeaksource/dailycommits/.

I think that the script will run on box4, except that it looks like the /usr/bin/mail client that we had on box2 does not exist, so possibly it is necessary to do "apt-get install mailutils".

So to get it running again, I think that the only thing required is to add a cron job for user squeaksource with the following entry:

55 23 * * * srv/box2/home/squeaksource/dailycommits/dailycommits.sh

That said, it looks like we do not yet actually have a user id "squeaksource" on box4, and for reasons that I cannot explain, the source.squeak.org home directory and everything under it are owned by user davidlewis (I did not do that, honest ;-).

So we probably need to add a proper user for squeaksource (source.squeak.org, not squeaksource.com), and we should change the file ownerships to match.

But in the near term, since I just happen to coincidentally be a person named davidlewis, I'll bet that I can reinstall the old dailycommits cron job under my user id.

I will see if I can install a mail client and cron job to get this working. Details will be in /root/admin-log.txt.

Dave

On 26.01.2015, at 16:32, Chris Muller asqueaker@gmail.com wrote:

...

Ah, what I said is probably not right. You are talking about the daily-digest aren't you? Not the individual commits, since we are still getting those.

On Mon, Jan 26, 2015 at 9:30 AM, Chris Muller ma.chris.m@gmail.com wrote:

...

cc:box-admins

My guess is we probably need to adjust the mail server settings in SqueakSource instance running source.squeak.org..?

---------- Forwarded message ---------- From: Eliot Miranda eliot.miranda@gmail.com Date: Mon, Jan 26, 2015 at 8:57 AM Subject: [Board] Daily Commit Log has disappeared To: Squeak Oversight Board Discussion board@lists.squeakfoundation.org

Hi All,

the Daily Commit Log has disappeared. I guess it's a job that has not been ported from the Herzer servers. It's really nice to be able to read just the daily report to keep abreast of trunk & inbox changes. Can we get it back?

Eliot (phone)

I haven't checked it yet, but I think cron jobs are not executed in the chroot environment, or if they are, then it's the lack of the mailer program which is responsible for the missing daily commit log.

On Mon, 26 Jan 2015, David T. Lewis wrote:

On Mon, Jan 26, 2015 at 07:44:33PM +0100, Bert Freudenberg wrote:

...

I think I did set up a cronjob to generate the daily commit log. The script probably was in my user dir. Did that survive?

• Bert -

Yes your script and the cron job have survived.

According to the cron entry at /srv/box2/var/spool/cron/crontabs/squeaksource, cron entry was this:

55 23 * * * /home/squeaksource/dailycommits/dailycommits.sh

Your dailycommits.sh script and everything that goes with it is safely restored in /srv/box2/home/squeaksource/dailycommits/.

I think that the script will run on box4, except that it looks like the /usr/bin/mail client that we had on box2 does not exist, so possibly it is necessary to do "apt-get install mailutils".

So to get it running again, I think that the only thing required is to add a cron job for user squeaksource with the following entry:

55 23 * * * srv/box2/home/squeaksource/dailycommits/dailycommits.sh

I don't think it's a good idea to trigger a script inside the chrooted environment from the outside. (It's been a while since I set up and used a chroot environment (probably in 2008), and since Tobias was kind enough to do it this time, I haven't brushed up my knowledge.)

That said, it looks like we do not yet actually have a user id "squeaksource" on box4, and for reasons that I cannot explain, the source.squeak.org home directory and everything under it are owned by user davidlewis (I did not do that, honest ;-).

The ownership information is kept as it was on box2. So what your id on box4 is is the same as what the id of the squeaksource user was on box2. Because of this, these files should only be used from the chroot environment.

So we probably need to add a proper user for squeaksource (source.squeak.org, not squeaksource.com), and we should change the file ownerships to match.

This must not be changed while it's being run inside the chroot environment. There is a separate user inside, which is being used for running the service. If the service is moved out of the chroot environment, then it'll need a new user on box4.

But in the near term, since I just happen to coincidentally be a person named davidlewis, I'll bet that I can reinstall the old dailycommits cron job under my user id.

You shouldn't do that. Mixing the chroot environment and the main environment is not a good idea.

Levente

I will see if I can install a mail client and cron job to get this working. Details will be in /root/admin-log.txt.

Dave

...

On 26.01.2015, at 16:32, Chris Muller asqueaker@gmail.com wrote:

...

Ah, what I said is probably not right. You are talking about the daily-digest aren't you? Not the individual commits, since we are still getting those.

On Mon, Jan 26, 2015 at 9:30 AM, Chris Muller ma.chris.m@gmail.com wrote:

...

cc:box-admins

My guess is we probably need to adjust the mail server settings in SqueakSource instance running source.squeak.org..?

---------- Forwarded message ---------- From: Eliot Miranda eliot.miranda@gmail.com Date: Mon, Jan 26, 2015 at 8:57 AM Subject: [Board] Daily Commit Log has disappeared To: Squeak Oversight Board Discussion board@lists.squeakfoundation.org

Hi All,

the Daily Commit Log has disappeared. I guess it's a job that has not been ported from the Herzer servers. It's really nice to be able to read just the daily report to keep abreast of trunk & inbox changes. Can we get it back?

Eliot (phone)

Hi David,

If you enter the chrooted environment, then the file will be at the right place (/home/squeaksource/dailycommits/) owned by the right user (squeaksource). If you run it from outside the environment, it'll probably behave differently, than running from inside.

The squeaksource user inside the chrooted environment can send email from commits@source.squeak.org to squeak-dev@lists.squeakfoundation.org, because that's exactly what the image does, when you upload a package.

I ran the script from the chrooted environment as the squeaksource user, but there were no changes today, so it didn't try to send an email.

On Tue, 27 Jan 2015, David T. Lewis wrote:

Hi Levente,

There is no chroot required.

The cron script does not need to run from the chroot environment. The only thing that I tried to change was the location of the script, which is now in /srv/box2/home/squeaksource/dailycommits/ instead of its original location in /home/squeaksource/dailycommits/. Aside from that, it is just a shell script that works with files in its own directory.

Note, there is a typo in my note below, the cron entry will be:

55 23 * * * /srv/box2/home/squeaksource/dailycommits/dailycommits.sh

As far as I know, the only problem right now is that the dailycommits.sh script tries to send mail to "commits@source.squeak.org", and this does not work. I do not know much about the mail system configuration, so

The script is trying to send the email from that address, not to that address.

Levente

I don't know how to solve that problem.

Thanks,

Dave

On Tue, Jan 27, 2015 at 08:31:38AM +0100, Levente Uzonyi wrote:

...

I haven't checked it yet, but I think cron jobs are not executed in the chroot environment, or if they are, then it's the lack of the mailer program which is responsible for the missing daily commit log.

On Mon, 26 Jan 2015, David T. Lewis wrote:

...

On Mon, Jan 26, 2015 at 07:44:33PM +0100, Bert Freudenberg wrote:

...

I think I did set up a cronjob to generate the daily commit log. The script probably was in my user dir. Did that survive?

• Bert -

Yes your script and the cron job have survived.

According to the cron entry at /srv/box2/var/spool/cron/crontabs/squeaksource, cron entry was this:

55 23 * * * /home/squeaksource/dailycommits/dailycommits.sh

Your dailycommits.sh script and everything that goes with it is safely restored in /srv/box2/home/squeaksource/dailycommits/.

I think that the script will run on box4, except that it looks like the /usr/bin/mail client that we had on box2 does not exist, so possibly it is necessary to do "apt-get install mailutils".

So to get it running again, I think that the only thing required is to add a cron job for user squeaksource with the following entry:

55 23 * * * srv/box2/home/squeaksource/dailycommits/dailycommits.sh

I don't think it's a good idea to trigger a script inside the chrooted environment from the outside. (It's been a while since I set up and used a chroot environment (probably in 2008), and since Tobias was kind enough to do it this time, I haven't brushed up my knowledge.)

...

That said, it looks like we do not yet actually have a user id "squeaksource" on box4, and for reasons that I cannot explain, the source.squeak.org home directory and everything under it are owned by user davidlewis (I did not do that, honest ;-).

The ownership information is kept as it was on box2. So what your id on box4 is is the same as what the id of the squeaksource user was on box2. Because of this, these files should only be used from the chroot environment.

...

So we probably need to add a proper user for squeaksource (source.squeak.org, not squeaksource.com), and we should change the file ownerships to match.

This must not be changed while it's being run inside the chroot environment. There is a separate user inside, which is being used for running the service. If the service is moved out of the chroot environment, then it'll need a new user on box4.

...

But in the near term, since I just happen to coincidentally be a person named davidlewis, I'll bet that I can reinstall the old dailycommits cron job under my user id.

You shouldn't do that. Mixing the chroot environment and the main environment is not a good idea.

Levente

...

I will see if I can install a mail client and cron job to get this working. Details will be in /root/admin-log.txt.

Dave

...

On 26.01.2015, at 16:32, Chris Muller asqueaker@gmail.com wrote:

...

Ah, what I said is probably not right. You are talking about the daily-digest aren't you? Not the individual commits, since we are still getting those.

On Mon, Jan 26, 2015 at 9:30 AM, Chris Muller ma.chris.m@gmail.com wrote:

...

cc:box-admins

My guess is we probably need to adjust the mail server settings in SqueakSource instance running source.squeak.org..?

---------- Forwarded message ---------- From: Eliot Miranda eliot.miranda@gmail.com Date: Mon, Jan 26, 2015 at 8:57 AM Subject: [Board] Daily Commit Log has disappeared To: Squeak Oversight Board Discussion board@lists.squeakfoundation.org

Hi All,

the Daily Commit Log has disappeared. I guess it's a job that has not been ported from the Herzer servers. It's really nice to be able to read just the daily report to keep abreast of trunk & inbox changes. Can we get it back?

Eliot (phone)