Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Migration issue? (The Doctor)
2. Re: Migration issue? (Julien ?LIE)
3. Re: Migration issue?
(Dave Shariff Yadallee - System Administrator a.k.a. The Root of the
Problem)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 Jul 2016 08:49:36 -0600
From: The Doctor <[email protected]>
To: Julien ??LIE <[email protected]>
Cc: [email protected]
Subject: Re: Migration issue?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Wed, Jul 20, 2016 at 09:41:38PM -0600, The Doctor wrote:
> On Wed, Jul 20, 2016 at 03:05:21PM -0600, The Doctor wrote:
> > On Wed, Jul 20, 2016 at 09:51:10PM +0200, Julien ??LIE wrote:
> > > Hi The Doctor,
> > >
> > >
> > > I indeed saw yesterday a few articles from you:
> > >
> > > Incoming Feeds (INN):
> > > Server Connects Offered Taken Refused Reject %Accpt
> > > Elapsed
> > > news.nk.ca 2 14 0 14 0 0%
> > > 01:09:28
> > >
>
> I wonder why groups.google.com have not picked up the articles?
>
> refused?
>
> > >
> > > And my server managed to connect to yours:
> > >
> > > Outgoing Feeds (innfeed) by Articles:
> > > Server Offered Taken Refused Reject Miss Spool %Took
> > > Elapsed
> > > news.nk.ca 1505 205 748 3 0 62 13%
> > > 21:52:49
> > >
> > >
> > >
> > > Did you try running inncheck?
> > > Are you using the FreeBSD port of INN or are you still building CURRENT?
>
> As I said, building current.
>
> Just notice something
>
> When I run the command
>
> su -m mews -c '/usr/local/news/bin/<command>' this works
> better than what the deafult port does.
>
> Who is in charge of the FreeBSD port?
Julien this is the key why the behaviour in FreeBSD is not working
as to expectatoin and I suspect
other BSDs have the same issue.
When I had to update inn on a daily basis in BSD/OS
I had to use
ctlinnd shutdown update ; pskill rc.news ; pskill innwatch ; pskill ovdb ;
pskill nnrpd ; pskill cnfsstat ; pskill innfeed ; gmake update ;
The pskill is from bash
And once the update was done I invoked
su -m -c news news -c ovdb_init -r ; su -m -c news news -c
/var/news/etc/rc.news ; ... su -m postgres -c '/usr/contrib/pgsql/bin/pg_ctl
start -D /usr/contrib/pgsql/data -l /usr/contrib/pgsql/serverlog -s' ; daemon
makehistory -O -x -F
The reason why I bring up the postrgres start is that
for postgres to start even in FreeBSD su -m <user> -c '<command>'
is the proper way to start said service dispite the port .
<Some noted problems were mentioned when I did search engine reasearch>
man su gives us
NAME
su -- substitute user identity
SYNOPSIS
su [-] [-c class] [-flms] [login [args]]
DESCRIPTION
The su utility requests appropriate user credentials via PAM and
switches
to that user ID (the default user is the superuser). A
shell is then
executed.
PAM is used to set the policy su(1) will use. In
particular, by default
only users in the ``wheel'' group can switch
to UID 0 (``root''). This
group requirement may be changed by
modifying the ``pam_group'' section
of /etc/pam.d/su. See
pam_group(8) for details on how to modify this
setting.
By default, the
environment is unmodified with the exception of USER,
HOME, and SHELL.
HOME and SHELL are set to the target login's default
values. USER
is set to the target login, unless the target login has a
user ID
of 0, in which case it is unmodified. The invoked shell is the
one
belonging to the target login. This is the traditional behavior of
su. Resource limits and session priority applicable to the original
user's login class (see login.conf(5)) are also normally retained unless
the target login has a user ID of 0.
The options are as follows:
-c class
Use the settings of the specified login class.
The login class
must be defined in login.conf(5).
Only allowed for the super-
user.
-f If the
invoked shell is csh(1), this option prevents it from
reading the ``.cshrc'' file.
-l Simulate a full login. The environment is discarded except for
HOME, SHELL, PATH, TERM, and USER. HOME and SHELL are modified
as above. USER is set to the target login. PATH
is set to
``/bin:/usr/bin''. TERM is imported
from your current environ-
ment. Environment
variables may be set or overridden from the
login class
capabilities database according to the class of the
target login. The invoked shell is the target login's, and su
will change directory to the target login's home directory.
Resource limits and session priority are modified to
that for the
target account's login class.
- (no letter) The same as -l.
-m Leave the environment
unmodified. The invoked shell is your
login shell, and
no directory changes are made. As a security
precaution, if the target user's shell is a non-standard shell
(as defined by getusershell(3)) and the caller's real uid is non-
zero, su will fail.
-s Set the MAC label to the user's default label
as part of the user
credential setup. Setting the MAC label
may fail if the MAC
label of the invoking
process is not sufficient to transition to
the user's
default MAC label. If the label cannot be set, su
will fail.
The -l (or -) and -m options are mutually exclusive; the last one speci-
fied overrides any previous ones.
If the optional args are provided on the command line, they are
passed to
the login shell of the target login. Note that all command
line argu-
ments before the target login name are processed by su
itself, everything
after the target login name gets passed to the login
shell.
By default (unless the prompt is reset by a
startup file) the super-user
prompt is set to ``#'' to remind one of
its awesome power.
ENVIRONMENT
Environment variables used by su:
HOME Default home directory of
real user ID unless modified as specified
above.
PATH Default
search path of real user ID unless modified as specified
above.
TERM Provides terminal type which may be retained for the substituted
user ID.
USER The user ID is always the effective ID (the target user
ID) after
an su unless the user ID is 0 (root).
FILES
/etc/pam.d/su PAM configuration for su.
EXAMPLES
su -m man -c catman
Starts a shell as user man, and
runs the command catman. You will
be asked for man's
password unless your real UID is 0. Note that
the -m
option is required since user ``man'' does not have a valid
shell by default. In this example, -c is passed to the shell of
ENVIRONMENT
Environment variables used by su:
HOME Default home directory of real user ID unless modified as
specified
above.
PATH Default search path of real user ID unless
modified as specified
above.
TERM Provides terminal type
which may be retained for the substituted
user ID.
USER The user ID
is always the effective ID (the target user ID) after
an su
unless the user ID is 0 (root).
FILES
/etc/pam.d/su PAM configuration for su.
EXAMPLES
su -m man -c catman
Starts a shell as user man, and runs the command catman. You
will
be asked for man's password unless your real UID is
0. Note that
the -m option is required since user
``man'' does not have a valid
shell by default. In this
example, -c is passed to the shell of
the user
``man'', and is not interpreted as an argument to su.
su -m man
-c 'catman /usr/share/man /usr/local/man'
Same as above, but the target command consists of more than a sin-
gle word and hence is quoted for use with the -c option being
passed to the shell. (Most shells expect the argument
to -c to be
a single word).
su -m -c staff man -c 'catman
/usr/share/man /usr/local/man'
Same as above, but the
target command is run with the resource
limits of the
login class ``staff''. Note: in this example, the
first -c option applies to su while the second is an argument to
the shell being invoked.
su -l foo
Simulate a login for user foo.
su - foo
Same as above.
su - Simulate a login for
root.
SEE ALSO
csh(1), sh(1), group(5),
login.conf(5), passwd(5), environ(7),
pam_group(8)
HISTORY
A su command
appeared in Version 1 AT&T UNIX.
FreeBSD 10.3
August 11, 2013 FreeBSD 10.3
This is why innd
is not behaving as expected, I think.
Is there a
workaround?
>
> > >
> >
> > Still seeing
> >
> > ctlinnd: No such site
> > [: : bad number
> > [: : bad number
> >
> > And innfeed is not starting up with innd on startup.
> >
>
> --
> Member - Liberal International This is doctor@@nl2k.ab.ca Ici
> doctor@@nl2k.ab.ca
> God,Queen and country!Never Satan President Republic!Beware AntiChrist
> rising!
> http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
> Language is the source of misunderstandings. -Antoine de Saint-Exupery
> _______________________________________________
> inn-workers mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/inn-workers
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism
Language is the source of misunderstandings. -Antoine de Saint-Exupery
------------------------------
Message: 2
Date: Thu, 21 Jul 2016 22:25:43 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Migration issue?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi The Doctor,
>> When I run the command
>>
>> su -m news -c '/usr/local/news/bin/<command>' this works
>> better than what the deafult port does.
>
>> Who is in charge of the FreeBSD port?
Looks like you could contact Johan van Selst (aka "johans"):
https://www.freshports.org/news/inn/
> When I had to update inn on a daily basis in BSD/OS
>
> I had to use
>
> ctlinnd shutdown update ; pskill rc.news ; pskill innwatch ; pskill ovdb ;
> pskill nnrpd ; pskill cnfsstat ; pskill innfeed ; gmake update ;
Why don't you just run "rc.news stop" as the news user?
You shouldn't have to kill innwatch, cnfsstat, innfeed, etc. (only nnrpd
if run in daemon mode)
> The reason why I bring up the postrgres start is that
> for postgres to start even in FreeBSD su -m <user> -c '<command>'
> is the proper way to start said service dispite the port .
Don't you use BerkeleyDB database with ovdb?
> ctlinnd: No such site
> [: : bad number
> [: : bad number
Isn't there a syntax problem in your newsfeeds file?
No error mentioned by "inncheck -a --pedantic"?
--
Julien ?LIE
? ? Tu n'as rien remarqu? d'?trange chez cet Arverne ?
? Oui, son accent. ? (Ast?rix)
------------------------------
Message: 3
Date: Thu, 21 Jul 2016 14:49:31 -0600
From: "Dave Shariff Yadallee - System Administrator a.k.a. The Root of
the Problem" <[email protected]>
To: Julien ??LIE <[email protected]>
Cc: [email protected]
Subject: Re: Migration issue?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Thu, Jul 21, 2016 at 10:25:43PM +0200, Julien ??LIE wrote:
> Hi The Doctor,
>
> >> When I run the command
> >>
> >> su -m news -c '/usr/local/news/bin/<command>' this works
> >> better than what the deafult port does.
> >
> >> Who is in charge of the FreeBSD port?
>
> Looks like you could contact Johan van Selst (aka "johans"):
> https://www.freshports.org/news/inn/
>
>
> > When I had to update inn on a daily basis in BSD/OS
> >
> > I had to use
> >
> > ctlinnd shutdown update ; pskill rc.news ; pskill innwatch ; pskill ovdb ;
> > pskill nnrpd ; pskill cnfsstat ; pskill innfeed ; gmake update ;
>
> Why don't you just run "rc.news stop" as the news user?
> You shouldn't have to kill innwatch, cnfsstat, innfeed, etc. (only nnrpd
> if run in daemon mode)
>
>
> > The reason why I bring up the postrgres start is that
> > for postgres to start even in FreeBSD su -m <user> -c '<command>'
> > is the proper way to start said service dispite the port .
>
> Don't you use BerkeleyDB database with ovdb?
>
>
> > ctlinnd: No such site
> > [: : bad number
> > [: : bad number
>
> Isn't there a syntax problem in your newsfeeds file?
> No error mentioned by "inncheck -a --pedantic"?
>
Looks like I need to get on a few FreeBSD porting committees!
The problem is that the start script of off.
It should be similar to the BSDI script
su -m - c new new -c '/path/to/rc.news' .
I would not be surprised if other BSD Unix system suffer from the same issue.
I no longer see the bad number error mentioned.
> --
> Julien ?LIE
>
> ? ? Tu n'as rien remarqu? d'?trange chez cet Arverne ?
> ? Oui, son accent. ? (Ast?rix)
> _______________________________________________
> inn-workers mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/inn-workers
--
For effective Internet Etiquette and communications read
http://catb.org/jargon/html/T/top-post.html, http://idallen.com/topposting.html
& http://www.caliburn.nl/topposting.html
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 85, Issue 5
******************************************
