[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Open questions regarding new messenger and secushare and organizatio
Re: Open questions regarding new messenger and secushare and organization Was: Make GNUnet Great Again
Thu, 23 Sep 2021 17:59:15 +0200
First I moved to config files to the right place,
then I ran "gnunet-arm -s". So I have to update the
config files to remove the UNIXONLY stuff.
sudo mv ./share/gnunet-secushare/config.d/multicast.conf
sudo mv ./share/gnunet-secushare/config.d/psycstore.conf
sudo mv ./share/gnunet-secushare/config.d/psyc.conf
sudo mv ./share/gnunet-secushare/config.d/social.conf
sudo mv ./lib/gnunet-secushare/libexec/gnunet-service-multicast
sudo mv ./lib/gnunet-secushare/libexec/gnunet-service-psycstore
sudo mv ./lib/gnunet-secushare/libexec/gnunet-service-psyc
sudo mv ./lib/gnunet-secushare/libexec/gnunet-service-social
2021-09-23T17:55:53.349364+0200 util-2309 WARNING Unknown or malformed
directive 'UNIXONLY' in line 9
2021-09-23T17:55:53.349429+0200 gnunet-arm-2309 ERROR Failed to parse
configuration file `/usr/local/share/gnunet/config.d/multicast.conf'
2021-09-23T17:55:53.349478+0200 util-2309 WARNING Failed to load base
configuration from '(null)'
2021-09-23T17:55:53.349494+0200 gnunet-arm-2309 ERROR Malformed
configuration. Exiting ...
On Thu, 2021-09-23 at 06:22 +0000, t3sserakt wrote:
> Hey Tobias,
> On 22.09.21 20:19, Tobias Platen wrote:
> > On Mon, 2020-11-16 at 09:28 +0100, t3sserakt wrote:
> > > Hey Bastian,
> > >
> > > thank you very much for your support.
> > >
> > > I like to explicitly invite you and everybody who likes to help
> > > some
> > > how
> > > to our monthly GNUnet meeting. This meeting is not exclusively
> > > for
> > > main
> > > developers or even developers at all. Do not expect us to find
> > > something
> > > for you to do immediately, because that is also a matter of
> > > resource
> > > allocation. There is enough to do, and we will find something.
> > >
> > > On 15.11.20 23:25, email@example.com wrote:
> > > > If I understand that right, we wouldn't had a problem here, at
> > > > all,
> > > > in the first place, if 3 GNUnet key components on which
> > > > secushare
> > > > development highly depends on, would be just fine: CADET, core
> > > > and
> > > > transport.
> > > It is mainly transport. For CADET I am quite sure it is working.
> > > > And as I got the impression, all these 3 components are in the
> > > > process of being revised to fit like that, but that process is
> > > > a
> > > > ton of work and therefore lasts long.
> > > We are only rewriting transport at the moment, which is indeed a
> > > lot
> > > of
> > > work. Part of that is making NAT traversal work much better,
> > > because
> > > sometimes peers have problems getting into the network initially.
> > > When
> > > we have something in place that is working (means unit test are
> > > not
> > > failing), we might think of testing this NAT traversal in as many
> > > as
> > > possible real world scenarios.
> > >
> > > Cheers
> > >
> > > t3sserakt
> > >
> > I just started hacking on gnunet-secushare, now the first thing
> > that I
> > need is starting the services. Those are installed in
> > /usr/local/lib/gnunet-secushare/libexec/.
> the mechanism how to start services is generic for all GNUnet
> You can configure which services shall be started. Configuration is
> in a configuration file
> If this configuration file is empty the default configuration is
> For each service there is a default configuration file. The
> for building the default configuration file for the secushare
> can be found here
> If you have started GNUnet with gnunet-arm
> START_ON_DEMAND = YES
> will start a service, if a client application is doing a request via
> service api.
> If you like to have the service started right from the beginning use
> IMMEDIATE_START = YES