search for: svv

On 11/14/05, CVS User aquette <nut-upsdev@lists.alioth.debian.org> wrote: > Update of /cvsroot/nut/nut/scripts/hotplug-ng > In directory haydn:/tmp/cvs-serv23053/scripts/hotplug-ng > > Log Message: > Directory /cvsroot/nut/nut/scripts/hotplug-ng added to the repository > --> Using per-directory sticky tag `Testing' Arnaud, can we add this directory to Development

Your mail to 'Nut-commits' with the subject CVS %1{sVv} Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this post...

...the CIA script, you have already switched to the new loginfo format. If not, you need to do now. For that you need to add UseNewInfoFmtStrings=yes to the CVS config file. Then if you have script using the old format you can escape it by using 1 after the % ie: ALL $CVSROOT/CVSROOT/syncmail %1{sVv} fribidi-commit@pdx.freedesktop.org After changing all of them, you still get teased by another warning message, suggesting you rewrite your scripts to use the new format. I did it for syncmail script and you can just copy. I changed the name of the script from 'syncmail' to 'maildif...

Hallo, Luke, Du meintest am 02.04.16: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE Perhaps a max protocol = NT1 in the glob...

...ol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > > > 2016-04-02 22:52 GMT+03:00 Helmut Hullen <Hullen at t-online.de>: > > > Hallo, Luke, > > > > Du meintest am 02.04.16: > > > > > Also, when I run testparm -svv | less I can find these four lines on > > > both the working and non-working servers: > > > > > server max protocol = SMB3 > > > server min protocol = LANMAN1 > > > client max protocol = NT1 > > > client min protocol...

OK, then here's the weird part. I have another server, hosting other files, lets my Windows 10 system connect. The main server won't though. They are both running Debian Jessie 8.3, and Samba 4.1.17-debian. Below is the /etc/samba/smb.conf file *that works with Windows 7 and 10*: [global] workgroup = SD57 netbios name = SAMBA server string = sss interfaces

On 02/04/16 20:02, Luke Barone wrote: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE > > > On Sat, Apr 2, 2016 at 11:57 AM...

Also, when I run testparm -svv | less I can find these four lines on both the working and non-working servers: server max protocol = SMB3 server min protocol = LANMAN1 client max protocol = NT1 client min protocol = CORE On Sat, Apr 2, 2016 at 11:57 AM, Luke Barone <lukebarone at gmail.com&g...

Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is