non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080603/1b43da99/attachment.bin>
On 06/02/08, Nicolas Williams wrote:
> On Mon, Jun 02, 2008 at 11:12:32AM +0100, Darren J Moffat wrote:
> > Raymond Xiong wrote:
> > >Two more notes on user authentication:
> > >
> > >1) ejabberd also supports PAM authentication. So it is possible to
> > >use UNIX accounts for ejabberd user authen
On Tue, 2008-06-03 at 10:58 -0400, James Carlson wrote:
> Mark Phalan writes:
> >
> > On Tue, 2008-06-03 at 09:49 -0400, James Carlson wrote:
> > > OK. Perhaps the file should be deleted on system upgrade, so that the
> > > user doesn't try to do something silly, like modify the file and
> > > e
Agreed. I stopped using logrotate when I moved to Solaris 9 and transitioned to
logadm. The big difference I see between the tools is the configuration file
syntax(logadm.conf is simpler) and the fact that logadm.conf contains the time
stamp info. Other than that, the functionality is the same.
On Tue, 3 Jun 2008, Ceri Davies wrote:
> I wonder if by "stable" you actually mean "unmaintained"? Sunfreeware
> is certainly not the originating community for logrotate, that's just
> somewhere the source file exists. As Sun's role is to "monitor the open
> source project", do they even know wh
Sebastien Roy writes:
> On Tue, 2008-06-03 at 13:08 -0700, Dean Roehrich wrote:
> > 1. Background
> >
> > Logrotate rotates log files and archives them in a central location.
>
> I find it odd that this case doesn't make mention of logadm(1M), the
> existing piece of architecture already in t
On Tue, 2008-06-03 at 09:49 -0400, James Carlson wrote:
> Mark Phalan writes:
> >
> > On Tue, 2008-06-03 at 09:28 -0400, James Carlson wrote:
> > > Wyllys Ingersoll writes:
> > > > With the latest resync of Kerberos with MIT Kerberos 1.6.3 (in
> > > > progress) kadmind(1M) reads the keys it needs
On Tue, 2008-06-03 at 13:08 -0700, Dean Roehrich wrote:
> 1. Background
>
> Logrotate rotates log files and archives them in a central location.
I find it odd that this case doesn't make mention of logadm(1M), the
existing piece of architecture already in the OS which is nearly
identical to
Jia Ni wrote:
>> My understanding from the above reference is that the pen program
>> itself does NOT read the /etc/pen.cf file by default (it does take -f
>> argument). In this case I highly recommend that the pen
>> configuration be via SMF properties able to be set per instance of
>> svc:/
I am sponsoring this case for Enrique Lopez-Pineda. It requests
a Minor binding and times out next Tuesday.
This is a Familiarity (key word) case and thus the FOSS checklist
is in the case materials directory along with the Man pages.
The upstream community is here: http://git.or.cz/
-- mark
Te
On Tue, 3 Jun 2008, Mark A. Carlson wrote:
> The "we already have X" argument does not apply to
> familiarity projects such as this one. If the Linux
> developer/admin doesn't find his favorite tool, he
> moves on...
>
> -- mark
It would apply if the tool in question conflicted with an existi
On Tue, 2008-06-03 at 09:28 -0400, James Carlson wrote:
> Wyllys Ingersoll writes:
> > With the latest resync of Kerberos with MIT Kerberos 1.6.3 (in
> > progress) kadmind(1M) reads the keys it needs directly from the
> > Kerberos database. Prior to this a keytab file had to be populated
> > with
Richard L. Hamilton wrote:
>> - Stack would be non-executable by default
> An advantage, certainly, although if someone is paranoid (and has no
> self-modifying code that would choke on it), this can be done for 32-bit with
> an /etc/system setting.
The ON consolidation, and some others, already e
Mark A. Carlson wrote:
> I am sponsoring this case for Enrique Lopez-Pineda. It requests
> a Minor binding and times out next Tuesday.
Thank you! Every X developer at Sun who has to use git to get
code from X.Org owes you whatever your favorite beverage is.
>Exported interface
s Sun's role is to "monitor the open
> source project", do they even know where it is? The logrotate utility
> doesn't appear to have a "homepage" on the world wide web, being
> maintained in Red Hat's CVS tree only so far as I can see [2].
>
> Ceri
>
> [1] NMFN; see above.
> [2] CVSROOT=:pserver:anonymous at rhlinux.redhat.com:/usr/local/CVS
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080603/fff82451/attachment.html>
On Tue, Jun 03, 2008 at 01:08:19PM -0700, Dean Roehrich wrote:
>
> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
> This information is Copyright 2008 Sun Microsystems
> 1. Introduction
> 1.1. Project/Component Working Name:
>logrotate
> 1.2. Name of Document Author/Supplier:
On Tue, Jun 03, 2008 at 01:08:19PM -0700, Dean Roehrich wrote:
> /usr/share/man/man8/logrotate.8 Uncommitted Man page
Nit: there's no manpage section 8 in Solaris. I think you want 1M here.
James Carlson wrote:
> > FYI, enable_extended_FILE_stdio(3C) is incompatible to many
> > applications, including coreutil. Using a FD > 256 crashes such
> > applications.
>
> "Coreutil"? As in GNU coreutils?
>
> If there's a problem here, and it's not just broken code in the
> application, then
"Garrett D'Amore" wrote:
> (As far as "something better", I think I prefer something along the
> lines of how AFS handles it, where $VARIABLE could be used within a
> symbolic link -- the kernel expands the variable when following the
> symlink. But we shouldn't try to design the solution he
"I. Szczesniak" wrote:
> > It's also lifted if you call enable_extended_FILE_stdio(3C), use the
> > extendedFILE.so.1 preload, or 'F' is used as the last character in the
> > fopen(3C) mode string.
>
> FYI, enable_extended_FILE_stdio(3C) is incompatible to many
> applications, including coreuti
Bart Smaalders wrote:
> x86 will for now need to deliver both 32 and 64 bit binaries. If you're
> worried
> about the performance issues involved w/ isaexec, then let's design
> something
If we start talking about isaexec, we should also talk about pfexec. I would
like to see the code moved
Closing this case as approved.
--Irene
Irene Huang wrote:
> Hi, all
>
> If there's any issues with this case, please reply with an email. If
> not, I am closing this case tomorrow as approved.
>
> Thanks
>
> --Irene
> On Thu, 2008-05-29 at 15:55 +0800, Jeff Cai wrote:
>
>> On Wed, 2008-05-28
Hmm... we already have logadm to rotate logs in Solaris today. Logcheck would
be more interesting. We don't have a built-in utility to scan logs for issues.
I have a pkg'd version of logcheck, if anyone is interested.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris
Was approved at last week's PSARC meeting.
Darren
Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
logrotate
1.2. Name of Document Author/Supplier:
Author: Colin Ngam
1.3 Date of This Document:
03 Ju
Alan Coopersmith wrote:
> Joseph Kowalski wrote:
> > I don't see why /usr/gnu/bin/awk should get preference over /usr/bin/awk
> > just because its in gnucore.
>
> How about because it's already known to be 64-bit clean since the GNU
> utilities run on platforms that are 64-bit only, while the Sol
Joerg Schilling wrote:
> If we start talking about isaexec, we should also talk about pfexec. I would
> like to see the code moved into the kernel. Other possible ways of getting
> rid
> of a userspace implementation for the pfexec features would be to implement
> something like capabilities th
The status of this case has been changed to 'waiting need spec'.
Dean
To make it clear on the record since it obviously wasn't to many people
given the slight incorrect language I used.
I do not believe this case qualified for self review or automatic
approval. Please submit a proposal and start a fast-track timer.
--
Darren J Moffat
Mark Phalan writes:
>
> On Tue, 2008-06-03 at 09:49 -0400, James Carlson wrote:
> > OK. Perhaps the file should be deleted on system upgrade, so that the
> > user doesn't try to do something silly, like modify the file and
> > expect it to do something.
>
> That might be a good idea (although lo
On Tue, Jun 03, 2008 at 10:58:29AM -0400, James Carlson wrote:
> I guess I was thinking more about what happens when things are
> restored from backup; the key will always be the one in the db, even
> if a different one is (somehow) given elsewhere. Perhaps that just
> doesn't happen in practice .
Mark Phalan writes:
>
> On Tue, 2008-06-03 at 09:28 -0400, James Carlson wrote:
> > Wyllys Ingersoll writes:
> > > With the latest resync of Kerberos with MIT Kerberos 1.6.3 (in
> > > progress) kadmind(1M) reads the keys it needs directly from the
> > > Kerberos database. Prior to this a keytab fi
Nicolas Williams wrote:
>
> Does ejabberd use OpenSSL?
>
Yes. Raymond has an approved OpenSSL contract for ejabberd.
There should be a contract-19 doc here for ejabberd. There's a space
for it:
http://sac.eng.sun.com/Archives/CaseLog/arc/PSARC/2003/500/contracts/
Raymond, John,
Can you update
On Tue, Jun 03, 2008 at 07:57:06PM +0800, Raymond Xiong wrote:
> ejabberd supports SASL(actually it always uses SASL so that client
> that doesn't support SASL cannot connect to it), but unfortunately
> it only suports very limited mechanisms: digest-md5, plain, and
> anonymous.
That's fine. S
Wyllys Ingersoll writes:
> With the latest resync of Kerberos with MIT Kerberos 1.6.3 (in
> progress) kadmind(1M) reads the keys it needs directly from the
> Kerberos database. Prior to this a keytab file had to be populated
> with the keys kadmind required. By default this file was located at
> /e
On Tue, Jun 03, 2008 at 12:21:27AM -0700, Dan Price wrote:
> If you need a hook in the zones framework, then let's figure out how
> to provide you one, rather than hacking something onto the side.
> Please come talk to the zones team before proceeding with this work,
> via zones-core at sun.com, or
> > I can think of three main categories of capacity
> limits on 32-bit that might
> > be higher on 64-bit:
> > * file size max of 2GB
> > * register size and usage
> > * available address space, and therefore amount
> that can be mmap()'d at once
> > (Also, IIRC stdio is supposed to handle > 256 f
On Wed 28 May 2008 at 02:54PM, Dean Roehrich wrote:
> All SAM-QFS packages will be updated with the following attributes and
> settings, to allow installs into the global zone and to prevent the
> install from propagating into non-global zones and prevent the package
> from
38 matches
Mail list logo
