On 11/08/2016 1:16 PM, Ngie Cooper wrote:
On Aug 10, 2016, at 22:05, O. Hartmann wrote:
I just checked the security scanning outputs of FreeBSD and found this
surprising result:
[...]
Checking for passwordless accounts:
polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
puls
> On 11 Aug 2016, at 14:35, O. Hartmann wrote:
> [...]
> Checking for passwordless accounts:
> polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
> pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
> saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/
> On 11 Aug 2016, at 15:36, O'Connor, Daniel wrote:
> My clamav and pulse users have a password field of * - i.e. they're disabled
> (AND the shell is nologin)
>
> I suspect this is a bug in the check not the ports.
Sorry, I just saw your next email, please disregard.
It does indeed look like
On Thu, 11 Aug 2016 15:29:03 +1000
Dewayne Geraghty wrote:
> Olivier,
> I've checked my 10.3Stable systems and they all have '*' as their password,
> which is consistent with /usr/ports/Mk/UIDs. You might like to check the
> age of the latter.
> Regards, Dewayne.
> PS Both ports and src were bui
Hi!
> I just checked the security scanning outputs of FreeBSD and found this
> surprising result:
>
> [...]
> Checking for passwordless accounts:
> polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
> pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
> s
> On Aug 10, 2016, at 22:05, O. Hartmann wrote:
>
> I just checked the security scanning outputs of FreeBSD and found this
> surprising result:
>
> [...]
> Checking for passwordless accounts:
> polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
> pulse::563:563::0:0:PulseAudi
I just checked the security scanning outputs of FreeBSD and found this
surprising result:
[...]
Checking for passwordless accounts:
polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin
pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
saned::194:194::0:0:SA
> A new transaction group (TXG) is created at LEAST every
> vfs.zfs.txg.timeout (defaults to 5) seconds.
> f you offline a drive for hours or more, it must have all blocks with a
> 'birth time' newer than the last transaction that was recorded on the
> offlined drive replayed to catch that drive u
On 10 Aug, Jung-uk Kim wrote:
> On 08/09/16 05:12 AM, Konstantin Belousov wrote:
>> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote:
>>> On 8 Aug, Konstantin Belousov wrote:
On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote:
> On Thursday, August 04, 2016 05:10:29 PM
On 08/09/16 05:12 AM, Konstantin Belousov wrote:
> On Mon, Aug 08, 2016 at 04:44:20PM -0700, Don Lewis wrote:
>> On 8 Aug, Konstantin Belousov wrote:
>>> On Mon, Aug 08, 2016 at 10:22:44AM -0700, John Baldwin wrote:
On Thursday, August 04, 2016 05:10:29 PM Don Lewis wrote:
> Reposted to -
On 8/7/16 5:44 PM, Don Lewis wrote:
> Adding PORTS_MODULES=emulators/virtualbox-ose-kmod recently broke on
> HEAD. When I do that I get this failure:
>
> ===> Ports module emulators/virtualbox-ose-kmod (all)
> cd ${PORTSDIR:-/usr/ports}/emulators/virtualbox-ose-kmod;
> PATH=/usr/obj/usr/src/
> t
On 8/10/16 4:18 AM, Peter Jeremy wrote:
> I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4
> r303811 and mosh to that host from my Linux laptop stopped working. All
> I get on the laptop is:
> $ mosh remotehost
> Connection to remotehost closed.
> /usr/bin/mosh: Did not fi
On 2016-08-04 07:22, Ultima wrote:
> Hello,
>
> I recently had some issue with a PSU and ran several scrubs on a pool with
> around 35T. Random drives would drop and require a zpool online, this found
> checksum errors. (as expected) However, after all the scrubs I ran, I think
> I may have found
On 8/10/16 4:18 AM, Peter Jeremy wrote:
> I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4
> r303811 and mosh to that host from my Linux laptop stopped working. All
> I get on the laptop is:
> $ mosh remotehost
> Connection to remotehost closed.
> /usr/bin/mosh: Did not fi
Am 10.08.2016 um 18:53 schrieb Ultima:
> Hello,
>
>> I didn't see any reply on the list, so I thought I might let you know
>
> Sorry, never received this reply (till now) xD
>
>>what I assume is happening:
>
>> ZFS never updates data in place, which affects inode updates, e.g. if
>> a file has
On 2016-08-10 12:53, Ultima wrote:
> Hello,
>
>> I didn't see any reply on the list, so I thought I might let you know
>
> Sorry, never received this reply (till now) xD
>
>> what I assume is happening:
>
>> ZFS never updates data in place, which affects inode updates, e.g. if
>> a file has bee
Hello,
> I didn't see any reply on the list, so I thought I might let you know
Sorry, never received this reply (till now) xD
>what I assume is happening:
> ZFS never updates data in place, which affects inode updates, e.g. if
> a file has been read and access times must be updated. (For that r
On Wed, Aug 10, 2016 at 10:49:40AM -0400, Matteo Riondato wrote:
>
> > On Aug 10, 2016, at 10:41 AM, Konstantin Belousov
> > wrote:
> > On Wed, Aug 10, 2016 at 10:33:23AM -0400, Matteo Riondato wrote:
> >> Hi all,
> >>
> >> I recently upgraded from a late June (pre 11-branch, as far as I can te
> On Aug 10, 2016, at 10:41 AM, Konstantin Belousov wrote:
> On Wed, Aug 10, 2016 at 10:33:23AM -0400, Matteo Riondato wrote:
>> Hi all,
>>
>> I recently upgraded from a late June (pre 11-branch, as far as I can tell)
>> revision to r303771.
>>
>> Now, running ???make update??? (or buildworld,
On Wed, Aug 10, 2016 at 10:33:23AM -0400, Matteo Riondato wrote:
> Hi all,
>
> I recently upgraded from a late June (pre 11-branch, as far as I can tell)
> revision to r303771.
>
> Now, running ???make update??? (or buildworld, ???) in /usr/src fails with a
> signal 12:
>
> matteo@triton:/usr/
Hi all,
I recently upgraded from a late June (pre 11-branch, as far as I can tell)
revision to r303771.
Now, running “make update” (or buildworld, …) in /usr/src fails with a signal
12:
matteo@triton:/usr/src$ sudo make update
Password:
*** Signal 12
Stop.
make: stopped in /usr/src
.ERROR_TAR
I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4
r303811 and mosh to that host from my Linux laptop stopped working. All
I get on the laptop is:
$ mosh remotehost
Connection to remotehost closed.
/usr/bin/mosh: Did not find mosh server startup message.
I've tried rebuildi
22 matches
Mail list logo