On 25.01.2015 04:54, Always Learning wrote:
>
> On Sat, 2015-01-24 at 22:45 -0500, Stephen Harris wrote:
>
>> On Sun, Jan 25, 2015 at 03:43:06AM +, Always Learning wrote:
>
>>> Should the 'correct' entry be:-
>>>
>>> fred:x:504:504:::/sbin/nologin ?
>>
>> No; that's invalid. There must
On Sat, January 24, 2015 9:54 pm, Always Learning wrote:
>
> On Sat, 2015-01-24 at 22:45 -0500, Stephen Harris wrote:
>
>> On Sun, Jan 25, 2015 at 03:43:06AM +, Always Learning wrote:
>
>> > Should the 'correct' entry be:-
>> >
>> >fred:x:504:504:::/sbin/nologin ?
>>
>> No; that's invalid
On Sat, 2015-01-24 at 22:45 -0500, Stephen Harris wrote:
> On Sun, Jan 25, 2015 at 03:43:06AM +, Always Learning wrote:
> > Should the 'correct' entry be:-
> >
> > fred:x:504:504:::/sbin/nologin ?
>
> No; that's invalid. There must be an entry in the home directory field.
Thanks Ste
On Sun, Jan 25, 2015 at 03:43:06AM +, Always Learning wrote:
> -M, do not create user's home directory
>
> so why do I see in /etc/passwd
>
> fred:x:504:504::/home/fred:/sbin/nologin
-M stops it doing a "mkdir" to create the actual directory in the
filesystem
> Should the 'corr
On Sun, 2015-01-25 at 04:38 +0100, Dennis Jacobfeuerborn wrote:
> On 25.01.2015 04:30, Always Learning wrote:
> >
> > useradd --help
> >
> > -d, --home-dir HOME_DIR home directory for the new user account
> > -M, do not create user's home directory
> > yet
> > useradd -M -s /sbi
On 25.01.2015 04:30, Always Learning wrote:
>
> useradd --help
>
> -d, --home-dir HOME_DIR home directory for the new user account
> -M, do not create user's home directory
> yet
> useradd -M -s /sbin/nologin FRED
>
> produces in /etc/passwd
>
> fred:x:504:504::/home/fred:
useradd --help
-d, --home-dir HOME_DIR home directory for the new user account
-M, do not create user's home directory
yet
useradd -M -s /sbin/nologin FRED
produces in /etc/passwd
fred:x:504:504::/home/fred:/sbin/nologin
Trying again with
useradd -d /dev/null -s /sb
On 01/24/2015 08:57 PM, Robert Nichols wrote:
With dual monitors, how do I control which monitor will get the greeter
display. I would really like to configure the screens as mirrored. Trying
to log in when the monitor with the greeter is not visible is very trying.
This is in CentOS 6. Sorry
With dual monitors, how do I control which monitor will get the greeter
display. I would really like to configure the screens as mirrored. Trying
to log in when the monitor with the greeter is not visible is very trying.
--
Bob Nichols "NOSPAM" is really part of my email address.
On Sat, Jan 24, 2015 at 12:32:01PM -0600, Valeri Galtsev wrote:
> One other thing I would try: disable selinux, and see if that lets
> apache read file, e.g.:
>
> setenforce 0
Setting SELinux to permissive temporarily is a good start, although
it's also helpful to check the audit logs, with:
au
On 01/24/2015 04:39 PM, Timothy Murphy wrote:
Actually, I appended both to /etc/postfix/mail.cf
--
mailbox_size_limit = 2000
message_size_limit = 1900
-
I don't know how big your mailbox is, but that seems like kind of a
small limit. In
On Sat, January 24, 2015 6:39 pm, Timothy Murphy wrote:
> Gordon Messmer wrote:
>
>> On 01/24/2015 07:10 AM, Timothy Murphy wrote:
>>>mailbox_size_limit = 2000
>>
>> I think you meant message_size_limit.
>
> Actually, I appended both to /etc/postfix/mail.cf
> --
> m
Gordon Messmer wrote:
> On 01/24/2015 07:10 AM, Timothy Murphy wrote:
>>mailbox_size_limit = 2000
>
> I think you meant message_size_limit.
Actually, I appended both to /etc/postfix/mail.cf
--
mailbox_size_limit = 2000
message_size_limit = 1900
---
Alexander Dalloz wrote:
> Am 24.01.2015 um 16:10 schrieb Timothy Murphy:
>> I'm getting repeated email (KMail) error messages
>> about one apparently over-large post:
>> --
>> Received: from helen.gayleard.com (localhost.localdomain [127.0.0.1]) by
>> helen.gayleard.com (Po
Andrew and Dennis are spot on.
Their conclusions about your server being connected to an access port and
not a trunk port would be my conclusion as well.
On Sat, Jan 24, 2015 at 9:11 AM, Dennis Jacobfeuerborn <
denni...@conversis.de> wrote:
> Hi Boris,
> what I'd like to know is the actual VLAN c
On 01/24/2015 07:10 AM, Timothy Murphy wrote:
mailbox_size_limit = 2000
I think you meant message_size_limit.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
On 01/24/2015 09:10 AM, Timothy Murphy wrote:
I'm getting repeated email (KMail) error messages
about one apparently over-large post:
--
Received: from helen.gayleard.com (localhost.localdomain [127.0.0.1]) by
helen.gayleard.com (Postfix) with ESMTP id E4500294A0 for
; Sat
On Sat, January 24, 2015 11:27 am, Tim Dunphy wrote:
> Hey guys,
>
> Unless you're using auditd (or a similar service) to watch the file,
> no. You could probably use the logs and `last` to see who was logged
> in at the time and make a guess.
>
>
>
> Also, you can look into shell history files (
Hey guys,
Unless you're using auditd (or a similar service) to watch the file,
no. You could probably use the logs and `last` to see who was logged
in at the time and make a guess.
Also, you can look into shell history files (though that might be cleaned
by users). Admin is allowed to do that
Am 24.01.2015 um 16:10 schrieb Timothy Murphy:
I'm getting repeated email (KMail) error messages
about one apparently over-large post:
--
Received: from helen.gayleard.com (localhost.localdomain [127.0.0.1]) by
helen.gayleard.com (Postfix) with ESMTP id E4500294A0 for
; Sa
I'm getting repeated email (KMail) error messages
about one apparently over-large post:
--
Received: from helen.gayleard.com (localhost.localdomain [127.0.0.1]) by
helen.gayleard.com (Postfix) with ESMTP id E4500294A0 for
; Sat, 24 Jan 2015 14:00:05 + (GMT)
Received: (
Hi Boris,
what I'd like to know is the actual VLAN configuration of the switch
port (link-type and tagged and untagged VLANs). When I look at the
switchport coniguration here I get (among other things):
...
Port link-type: trunk
Tagged VLAN ID : 8, 1624
Untagged VLAN ID : 10
...
Here is my
Hi Boris,
Is the switch port mode tagged or untagged.
Thanks,
Andrew
On 24 January 2015 at 13:35, Boris Epstein wrote:
> Do you need the whole configuration? On the switch end, we have the
> relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and
> the range of ports (Gi1/0
Do you need the whole configuration? On the switch end, we have the
relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and
the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN.
Seems - and acts - like a legitimate setup and works fine, except for this
particular instanc
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ..
25 matches
Mail list logo