Hello everybody!

I have a point setup here that needs to use a filebox. That is working as it should, but I also have the dailyBundles on turned on, yet husky isn't creating one
echomail bundle for that day. It's creating a bundle each run.

Am I missing something in my config for the link or husky's config in general.

#--in the general config--

FileBoxesDir /path/to/filebox


#--links config--

Link Zeus-Agora
Aka 46:3/101.5
ourAka 46:3/101
EchoMailFlavour hold
forwardRequests on
allowEmptyPktPwd on
accessgrp G
pktpwd
ReducedSeenBY on
packer zip
FileBox /path/to/file/filebox/zeus
TickerPackToBox on
fileBoxAlways yes
fileEchoFlavour hold
netMailFlavour hold
dailyBundles on





Stephen


--- GoldED+/LNX 1.1.5-b20180707
* Origin: Dragon's Lair BBS, Telnet: dragon.vk3heg.net (3:633/280)

On 15.9.2021 9.43, Stephen Walsh wrote:

I have a point setup here that needs to use a filebox. That is
working as it should, but I also have the dailyBundles on turned on,
yet husky isn't creating one echomail bundle for that day. It's
creating a bundle each run.

Am I missing something in my config for the link or husky's config in general.

I understand this filebox thing so that if something is put into a filebox once, it cannot be changed. Any program can read and delete it any time. So HPT has to create more and more arcmail bundles.

I recommend 'packer none' for filebox links. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Tommi wrote (2021-09-15):

I understand this filebox thing so that if something is put into a
filebox once, it cannot be changed. Any program can read and delete it
any time. So HPT has to create more and more arcmail bundles.

How is that different to arcmail bundles referenced in a FLO file?

I recommend 'packer none' for filebox links. :)

I always recommend uncompressed PKTs. binkp can compress with gzip and bzip2.

---
* Origin: 1995| Invention of the Cookie. The End. (2:280/464.47)

Hello, Oli.
On 15/09/2021 11.38 you wrote:

Tommi wrote (2021-09-15):

I understand this filebox thing so that if something is put into a filebox once, it cannot be changed. Any program can read and delete it any time. So HPT has to create more and more arcmail bundles.

How is that different to arcmail bundles referenced in a FLO file?

Files in BSO can be locked.

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi Oli,

On 2021-09-15 11:38:25, you wrote to Tommi Koivula:

I understand this filebox thing so that if something is put into a
filebox once, it cannot be changed. Any program can read and delete
it any time. So HPT has to create more and more arcmail bundles.

How is that different to arcmail bundles referenced in a FLO file?

Access to files in a regular BSO directory is strictly regulated through the use of lock files (*.csy, *.bsy). So different programs won't access the same files at the same time. There is no such standard for fileboxes.

I recommend 'packer none' for filebox links. :)

I always recommend uncompressed PKTs. binkp can compress with gzip and bzip2.

I recommend not using fileboxes at all. ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On 15.9.2021 12.53, Wilfred van Velzen wrote:

I understand this filebox thing so that if something is put into a
filebox once, it cannot be changed. Any program can read and delete
it any time. So HPT has to create more and more arcmail bundles.

How is that different to arcmail bundles referenced in a FLO file?

Access to files in a regular BSO directory is strictly regulated through the use of lock files (*.csy, *.bsy). So different programs won't access the same files at the same time. There is no such standard for fileboxes.

I recommend 'packer none' for filebox links. :)

I always recommend uncompressed PKTs. binkp can compress with gzip and bzip2.

I recommend not using fileboxes at all. ;)

The start point of this discussion was: "...that needs to use a filebox". ;)

'Tommi

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi Tommi,

On 2021-09-15 15:32:10, you wrote to me:

I recommend not using fileboxes at all. ;)

The start point of this discussion was: "...that needs to use a filebox". ;)

Hence the smiley... But "needs", needs to be explained, to know for sure. ;-)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On 15.9.2021 13.38, Oli wrote:

I recommend 'packer none' for filebox links. :)

I always recommend uncompressed PKTs. binkp can compress with gzip and bzip2.

There are other ways to transfer mail bundles than binkp/d. I use filebox to send mail from one tosser to another in a same computer.

And compressing is not relevant. If you put mail on hold for a point, you might want to combine all the thousands of tiny .pkt's in one file. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

On 15.9.2021 15.42, Wilfred van Velzen wrote:

I recommend not using fileboxes at all. ;)

The start point of this discussion was: "...that needs to use a filebox".
;)

Hence the smiley... But "needs", needs to be explained, to know for sure. ;-)

Absolutely! :D

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)

Wilfred wrote (2021-09-15):

Hi Oli,

On 2021-09-15 11:38:25, you wrote to Tommi Koivula:

I understand this filebox thing so that if something is put into a
filebox once, it cannot be changed. Any program can read and delete
it any time. So HPT has to create more and more arcmail bundles.

How is that different to arcmail bundles referenced in a FLO file?

Access to files in a regular BSO directory is strictly regulated through the use of lock files (*.csy, *.bsy). So different programs won't access the same files at the same time. There is no such standard for fileboxes.

True, no formal standard. But it's obvious that the program should lock the file before modifying it or when a transfer is in progress. No idea how binkd and hpt handles fileboxes though. I safe strategy would be to lock all files in a filebox when a session starts (at the same time the *.bsy file is written).

As fileboxes usually don't replace BSO, but working in addition to BSO, the program modifying anything in the filebox can create a .bsy file in the BSO.

Of course we cannot rely on such behaviour, because there is no standard. But from the tossers perspective it shouldn't be a problem to safely create / modify 'dailyBundles' in fileboxes. Just create a *.bsy file.



https://en.wikipedia.org/wiki/File_locking

"Windows inherits the semantics of share-access controls from the MS-DOS system, where sharing was introduced in MS-DOS 3.3 . Thus, an application must explicitly allow sharing when it opens a file; otherwise it has exclusive read, write, and delete access to the file until closed (other types of access, such as those to retrieve the attributes of a file are allowed.)"

"Unix-like operating systems (including Linux and Apple's macOS) do not normally automatically lock open files.
[...]
Although some types of locks can be configured to be mandatory, file locks under Unix are by default advisory. This means that cooperating processes may use locks to coordinate access to a file among themselves, but uncooperative processes are also free to ignore locks and access the file in any way they choose. In other words, file locks lock out other file lockers only, not I/O.
[...]
For this reason, some Unix-like operating systems also offer limited support for mandatory locking.[6] On such systems, a file whose setgid bit is on but whose group execution bit is off when that file is opened will be subject to automatic mandatory locking if the underlying filesystem supports it."

---
* Origin: 1995| Invention of the Cookie. The End. (2:280/464.47)

Hi Oli,

On 2021-09-15 14:41:18, you wrote to me:

How is that different to arcmail bundles referenced in a FLO file?

Access to files in a regular BSO directory is strictly regulated
through the use of lock files (*.csy, *.bsy). So different programs
won't access the same files at the same time. There is no such
standard for fileboxes.

True, no formal standard. But it's obvious that the program should lock the
file before modifying it or when a transfer is in progress. No idea how binkd and hpt handles fileboxes though. I safe strategy would be to lock all files in a filebox when a session starts

It's not safe. As you show in the wikipedia quotes on file locking, it's cooperative on unix-like os's.

(at the same time the *.bsy file is written).

There are no *.bsy files written in fileboxes.

As fileboxes usually don't replace BSO, but working in addition to
BSO, the program modifying anything in the filebox can create a .bsy
file in the BSO.

It could, but it doesn't accomplish anything, because they will be ignored by other processes accessing the filebox.

Of course we cannot rely on such behaviour, because there is no
standard.

Indeed. So don't rely on it, period.

But from the tossers perspective it shouldn't be a problem to safely create / modify 'dailyBundles' in fileboxes. Just create a *.bsy file.

And that wouldn't help at all, when those *.bsy files are ignored by other processes accessing the filebox...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Tommi!

15 Sep 21 11:42, you wrote to me:

Am I missing something in my config for the link or husky's config
in general.

I recommend 'packer none' for filebox links. :)

Thanks, Tommi.. Just changed the config and will test.



Stephen


--- GoldED+/LNX 1.1.5-b20180707
* Origin: Dragon's Lair BBS, Telnet: dragon.vk3heg.net (3:633/280)

Hi Wilfred!

Wednesday September 15 2021 12:53, you wrote to Oli:

I recommend not using fileboxes at all. ;)

However, it can be useful for sending mail to local systems.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

17 Sep 21 10:35, Stephen Walsh wrote to Tommi Koivula:

Am I missing something in my config for the link or husky's config
in general.

I recommend 'packer none' for filebox links. :)

Thanks, Tommi.. Just changed the config and will test.

And now you should have 112 .pkt's instead of 112 arcmail bundles. ;)

What is the reason you need to use filebox ?

'Tommi

---
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1)

17 Sep 21 09:20, Stas Mishchenkov wrote to Wilfred van Velzen:

Wednesday September 15 2021 12:53, you wrote to Oli:

I recommend not using fileboxes at all. ;)

However, it can be useful for sending mail to local systems.

It is. I have a local link between HPT 2:221/1 and GEcho 2:221/360. Hpt puts mail to 2:221/360 into the inbound directory of GEcho as .pkts.

GEcho cannot do the same, another program needed to move mail from BSO to the inbound of HPT.

'Tommi

---
* Origin: 2a01:4f9:c011:1ec5:f1d0:2:221:1 (2:221/1)